My guess is that it was done using shadows to not interfere with the
native look, but actually this just works even with native-looking menus
(like the <select> menulist), because the background-color for those is
set on the menupopup, rather than the ::part(content).
So those have effectively 1px of extra padding (due to the transparent
border), but that seems barely perceptible, and worth the consistency
and simplification.
Differential Revision: https://phabricator.services.mozilla.com/D164716
Previously this would dispatch to the current thread, which could in
some cases be a threadpool thread, meaning that the runnable would
not run until the threadpool thread exits. This switches the code over
to always dispatch to the StreamTransportService instead.
Depends on D161349
Differential Revision: https://phabricator.services.mozilla.com/D164504
I was unable to get gnome searching working at all on my machine (perhaps it's broken on Ubuntu?), thus I was unable to verify this fix myself -- but it seems pretty straightforward and safe to take.
Differential Revision: https://phabricator.services.mozilla.com/D164902
This will mean that we drain direct tasks immediately after executing
things like native OS messages through OnProcessNextEvent, and also that
we drain direct messages immediately when entering a nested event loop,
rather than after processing the first runnable in that nested event
loop. This should make the behaviour a bit more consistent.
Differential Revision: https://phabricator.services.mozilla.com/D164839
This adds the <moz-support-link> custom element as well as stories and
tests for this reusable component. The purpose of this component is to
replace individual implementations of the "Learn more" links present
in Firefox, specifically in about:preferences and about:addons.
See Bug 1801927 for an instance of using this component to refactor
the "Learn more" links in about:preferences#general.
Differential Revision: https://phabricator.services.mozilla.com/D164131
Just disable in the build config for now. It is unlikely that any issues will
come up since this is disabled in release but just in case this will allow us
to re-enable it quickly.
Differential Revision: https://phabricator.services.mozilla.com/D164565
The data race is happening, because `nsHttpTransaction::ParseLineSegment`
can be called before `nsHttpTransaction::AsyncRead`. Initializing it in
`nsHttpTransaction::Init` removes the race condition.
Should fix most early hint intermittent:
* Bug 1744028
* Bug 1746324
* Bug 1760124
* Bug 1775763
* Bug 1803884
Differential Revision: https://phabricator.services.mozilla.com/D164321
Just disable in the build config for now. It is unlikely that any issues will
come up since this is disabled in release but just in case this will allow us
to re-enable it quickly.
Differential Revision: https://phabricator.services.mozilla.com/D164565
If the UA sheet gets parsed with the pref off, and then the pref gets
flipped on, we don't re-parse the UA sheet (nor we want to).
Enable the property in UA sheets unconditionally so that the test passes
even when the browser was started-up with the container queries pref
off.
Differential Revision: https://phabricator.services.mozilla.com/D164823
Just disable in the build config for now. It is unlikely that any issues will
come up since this is disabled in release but just in case this will allow us
to re-enable it quickly.
Differential Revision: https://phabricator.services.mozilla.com/D164565
