| Commit message (Collapse) | Author | Age |
|\
| |
| |
| | |
caret_color
|
| |
| |
| |
| | |
Presentation of a document is destroyed.
|
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
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.
|
| | |
|
|/
|
|
| |
Mozilla's original implementation of this failed a couple of tests, but this seems to solve all the problems. Basically, the caret-color wasn't able to be set differently based on whether a link was visited, and the auto value implementation was incomplete. The only test we fail now is the one where you have grey text on a grey background and the caret is supposed to be visible, but I think that may have been removed from the spec. Even if it wasn't, no other browser supports it anyway.
|
| |
|
|
|
|
|
| |
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
|
| |
|
|\ |
|
| |
| |
| |
| | |
release build assertions for mismatching compartments.
|
| | |
|
| |
| |
| |
| | |
This hooks up module scripts to the existing preload mechanism.
|
| | |
|
| | |
|
|/
|
|
|
|
|
| |
Unless a user is debugging media errors, this detail is unnecessary to report
and could include sensitive data which could be abused by third-party
requesters. This aligns it with the standard success/error paradigms in normal
browsing situations.
|
|
|
|
| |
Ref: BZ 1382020
|
|
|
|
|
|
|
|
|
|
| |
This commit does several things:
- Moves the pref check from ScriptLoader to ns[I]Document so it can be called on
the document.
- Changes the atrribute freezing function to a better name that takes the
document as a parameter.
- Sets the proper async/defer attributes on HTML script elements based on
keywords and whether they are module scripts or not.
|
|
|
|
|
|
| |
This simplifies handling of combinations of async/defer by assigning one and
only one state to scripts.
If async then always async > if defer or module then defer > otherwise blocking.
|
|
|
|
|
|
| |
This makes sure we don't block body-referred sub-resources by head-referenced
defer and async scripts. This is important for all script loads, not just
modules, but is added here because it was run into while implementing modules.
|
| |
|
| |
|
|
|
|
| |
Because the spec says so.
|
| |
|
|
|
|
| |
module map after fetch errors.
|
| |
|
| |
|
|
|
|
| |
Because the spec says so.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Keyboard.jsm back in EXTRA_JS_MODULES
JSMs are NOT Components.
|
| |\
| | |
| | | |
Respond to disabled attribute set on <link> elements from HTML
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is not very "clean," and is mostly done in the same sloppy way as Emilio did it because that's basically the only way you can do it. Note well that this does NOT actually turn off everything I've done in a clean fashion like ifdefs would. For instance, the Explicitly Enabled flag is still present, but is now always false because the only condition that can set it true is behind the pref and therefore inert when this pref is off. Also, because the arguments of SetDisabled have changed, my modifications to SetMozDisabled must be present regardless of whether the pref is on or off. What I have done is turn off the actual reflection of the disabled attribute in Disabled and SetDisabled, as well as in AfterSetAttr.
However, turning the pref off seems to restore more or less our old behavior, though there may be subtle differences unlike with an ifdef since this is, unfortunately, not an exact science and I can only turn off changes that happen within individual functions and not changes in how functions interact with each other.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This part of the bug was significantly complicated by the following major refactors:
https://bugzilla.mozilla.org/show_bug.cgi?id=1456435
https://bugzilla.mozilla.org/show_bug.cgi?id=1459498
As best as I can tell, we just need to implement the explicitly enabled
flag on every instance of GetStyleSheetInfo, make sure
aIsExplicitlyEnabled is false in every situation except the one where
the disabled content attribute is removed from a link element, and
enable alternate stylesheets if this flag is set on them. So we take the
explicitly enabled flag as an input to PrepareSheet, and also add it to
LoadStyleLink and LoadInlineStyle. I also decided not to defer loading of
alternate stylesheets that have been explicitly enabled.
|