| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
| |
This aligns with the current spec regarding overflow-wrap: break-word and
overflow-wrap: anywhere in if it affects intrinsic sized due to considering
soft-wrap opportunities or not.
See CSS Text Module Level 3, Editor’s Draft, 1 October 2020, Section 5.5
|
|
|
|
| |
intrinsic size.
|
|
|
| |
Revise Commit message style and add Follow-up form
|
|\
| |
| | |
Remove excessive VARIANT_OPACITY statements.
|
|/
|
|
|
|
|
|
| |
I got very anxious about making sure I included VARIANT_OPACITY in all the places VARIANT_NUMBER was included to make sure it couldn't possibly break unexpectedly, and that led to me accidentally breaking a mechanism that prevented percentages from serializing as numbers in other parts of the code. It was a total accident, and these additions were unnecessary. Basically, the situation is that there was one part of the code where it determines what's allowed for the flex statement (and possibly other statements) by checking whether it got stored as a "number", and basically only disallows percentages if it attempted to store/serialize them as percentages.
However, it only got to that part of the code because I accidentally allowed VARIANT_OPACITY as a valid way for certain tokens to parse where it wasn't necessary. If it tries to parse it that way under very specific circumstances... percentages will be marked valid and fed through the system as numbers rather than being rejected and not serialized at all, because the check to disallow percentages there relied on them being stored as percentages.
It's a really weird thing to have a problem with in a lot of ways, because if percentages aren't allowed in a field, you would think people wouldn't try to use them there, much less depend on the broken behavior that results from them not parsing as a related value.
|
|
|
|
| |
This fixes some crashing scenarios.
|
|
|
|
|
|
|
| |
ResizeObserverNotificationHelper::Unregister
A race condition seemed to exist between tab destruction and un-registering a ResizeObserver resulting in a null deref crash.
The original reporter in Forum Topic 25311 experienced this on msn.com so that was the functional test reference.
|
|\
| |
| | |
Issue #1656 - Fix broken comment from Part 1
|
|/
|
|
| |
Removing the vim line unintentionally broke the comment leading to build failure, this restores the comment.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Another S&R run with some smarter matching.
|
| |
|
|
|
|
| |
The poor fellows got lost in an ASCII-interpretation of the world.
|
|
|
|
|
|
| |
Since these are just interpreted comments, there's 0 impact on actual code.
This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are
a few others scattered around which will be removed manually in a second part.
|
| |
|
|
|
|
|
|
|
| |
This make MediaQueryList inherit from EventTarget and adds MediaQueryListEvent
as an interface as well as the onchange() method.
This should not affect compatibility with other code; the event object is a
MediaQueryListEvent instance, which is recognized as a MediaListQuery instance.
|
|
|
|
|
| |
This DiD measure ensures that our async HRTF database loading is completed
before we actually try to use it. If not done, database() simply returns null.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Implement percentage for CSS opacity keywords
|
| |
| |
| |
| | |
Even though percentages are already treated as floats internally by the style system for computation purposes, you have to go out of your way to stop them from being read back out as percentages. What I do here amounts to storing the percentage token in the "wrong" container, the one normally used for floats. This allows a value that was read in as a percentage to be read back out as something else, which is normally prevented by the design of the style system.
|
| |
| |
| |
| |
| | |
This preliminary step allows percentages to be computed and display correctly,
but unfortunately it fails a test after changing VARIANT_HN to VARIANT_HPN because that allows values to be serialized as percentages. However, not doing this means percentages are rejected as valid values for the user to input. The way the style system is setup makes it hard to change this for opacity without changing it for everything else, especially since some code-saving speed hacks in Bug 636029 and Bug 441367 that make a lot of assumptions about this stuff very rigid.
|
| |
| |
| |
| |
| | |
This excludes DOMProxy handlers in dom bindings because that's intertwined with
codegen and js that needs to be handled together.
|
| | |
|
| |
| |
| |
| |
| | |
Instead of doing the whole dll-load, replace function dance, we can just use the
shlobj.h version of Windows.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Implements ResizeObserver, ResizeObserverEntry and ResizeObservation
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Clear the module map - Debug Followup
|
|/ /
| |
| |
| |
| |
| | |
An assertion was added to dom/script/ScriptLoader.cpp but fails to compile on debug builds due it not being included in the namespace.
Ref: BZ 1529203
|
|\|
| |
| | |
Clean up local variables from <link> disabled issue.
|
| |
| |
| |
| | |
Since the local variable is always initialized to false, we don't actually need to declare it and can just pass "false" directly as a parameter to the PrepareSheet function's bool. I was worried about code readability at first, but some well-placed comments took care of that.
|
| |
| |
| |
| | |
This clarifies the assumptions the code is making and the order in which the variables pass through the loading process. The new variable is set after the sheet is created and prepared, and is assumed to be false in the beginning.
|
| |
| |
| | |
* Issue #457 - Fix usage of a macro in a cocoa widget
|
| |
| |
| |
| |
| |
| | |
There are situations where nsCSSClipPathinstance->CreateClipPath(dt)
returns null. We need to check for this before trying to use its
functions. If there is no clip path, then always return "no hit".
|
|\ \
| | |
| | | |
Remove hostname parameter to trust domain.
|
|/ /
| |
| |
| |
| |
| | |
Host name was purely being used for HPKP and since HPKP is killed,
this can also go. Currently it doesn't do anything other than
generating build warnings.
|
|\ \ |
|
| | |
| | |
| | |
| | | |
release build assertions for mismatching compartments.
|
| | | |
|