As per https://drafts.csswg.org/css-will-change/#will-change.
> If any non-initial value of a property would cause the element to
> generate a containing block for absolutely positioned elements,
> specifying that property in will-change must cause the element to
> generate a containing block for absolutely positioned elements.
But in this case the transform property wouldn't apply to the element so
there's no reason to create a stacking-context.
Differential Revision: https://phabricator.services.mozilla.com/D114121
Especially with BFCache enabled for Fission there is no new
browsing context created when a page comes out of the cache.
As such the current logic to detect remoteness changes doesn't
work. Instead the "XULFrameLoaderCreated" event on the tabbrowser
object can be used instead, which is always fired.
Differential Revision: https://phabricator.services.mozilla.com/D113769
When there is a browsing context change the order of page load
events is not guaranteed. As such a "pagehide" event from the
current page might be received after a "pageshow" event from
the target page.
Differential Revision: https://phabricator.services.mozilla.com/D113768
This will be used by a later patch in the stack, but can likely be used in more
places in the future.
Depends on D114604
Differential Revision: https://phabricator.services.mozilla.com/D114605
We have some settings that we don't handle well if they change
at runtime. Make them mirror:once.
In the case of `wideget.wayland_vsync.enabled`, this was practically
already the case but in a deprecated way. While on it, use the chance to
rename it to `widget.wayland.vsync.enabled` so it matches other
configs.
Differential Revision: https://phabricator.services.mozilla.com/D114664
It's needed to independently print messages for CDP and/or
WebDriver BiDi depending on which protocol is actually active.
Differential Revision: https://phabricator.services.mozilla.com/D114572
Symbols are information on the structure of a given script (assignments, functions,
expressions, …)
This patch handles scripts using private fields and fixes a few things in the debugger:
- we get the full expression when hovering a private property access,
a prerequisite to get the value of a private propery in the variable tooltip
(which will be handled in Bug 1709567).
- private methods now show up in the outline view under their proper name, and
not `anonymous`. `simplifyDisplayName` was fixed as well to not strip the `#`
at the start of the method name.
Tests are added to ensure this works as expected.
A side-effect from modifying examples/simple1.js is that browser_dbg-outline-pretty.js
was broken since pretty-fast wasn't able to parse file with private fields syntax.
pretty-fast is updated to its latest version and the pretty-print worker is updated
so the test does not break anymore.
Depends on D114345
Differential Revision: https://phabricator.services.mozilla.com/D114459
When Bug 1701451 happened, Negative height was passed to nsWindow::Resize(). It is helpful to call gfxCriticalNoteOnce when it happens.
Differential Revision: https://phabricator.services.mozilla.com/D114704
The very first navigation wasn't using navigateTo and that caused some exception
because we were trying to use previous target's memory front which was already destroyed.
I also removed this now uncessary fork of navigateTo.
Differential Revision: https://phabricator.services.mozilla.com/D114478
- Keep strong popup hierarchy from both layout and widget perspective and use only
topmost popups as parents for newly opened popups.
- Always close popup windows with all opened child popups.
- Always close tooltip windows when new popup is created.
- Introduce 'WidgetPopup' log to trace popups changes.
- Export correct window roles (Toplevel, Popup, Dialog).
Differential Revision: https://phabricator.services.mozilla.com/D114578
There are only two failing tests. First one bug908915.js failed because of
the lack of OSObject.cpp::ResolvePath support for wasi. The second one is failed
because it exceeds the recursion limit.
Differential Revision: https://phabricator.services.mozilla.com/D114325
This makes it easier to understand and will make it easier to not include 'extra' frames (as we're hoping they will coalesce with the original frame on the compositor).
Differential Revision: https://phabricator.services.mozilla.com/D113736
This makes it easier to understand and will make it easier to not include 'extra' frames (as we're hoping they will coalesce with the original frame on the compositor).
Differential Revision: https://phabricator.services.mozilla.com/D113736
Some of the changes in bug 1626083 result in a more deterministic flow that uncovers a race
and an incorrect underlying assumption in the test.
The underlying assumption is that clearing mode on shutdown is disabled in tests, which is false - it's enabled.
The race is that we assume that the mode is already 0 and try to ensure it doesn't change, whereas it actually
starts empty (undefined) and changes to 0, because of the incorrect underlying assumption.
This mistake only exists in browser_cleanFlow.js, the other tests are correctly waiting for the final TRR mode
without trying to ensure no change.
Differential Revision: https://phabricator.services.mozilla.com/D114592
And since, when present, these are the colors for a selected cell, use
them for HTML cell highlight colors (the <select multiple> ones).
Depends on D114392
Differential Revision: https://phabricator.services.mozilla.com/D114393
As it won't get enough contrast anyways. This is what Gecko does on macOS where
selection colors are also semi-transparent.
Depends on D114391
Differential Revision: https://phabricator.services.mozilla.com/D114392
