ChromeUtils::GetLibcConstants() is a replacement for
nsIOSFileConstantsService providing OS.Consts.LIBC. The constants from
OS.Consts.Win have been inlined into subprocess_shared_win.js, since it was
already defining several other constants and it was the only consumer.
Differential Revision: https://phabricator.services.mozilla.com/D180358
ChromeUtils::GetLibcConstants() is a replacement for
nsIOSFileConstantsService providing OS.Consts.LIBC. The constants from
OS.Consts.Win have been inlined into subprocess_shared_win.js, since it was
already defining several other constants and it was the only consumer.
Differential Revision: https://phabricator.services.mozilla.com/D180358
ChromeUtils::GetLibcConstants() is a replacement for
nsIOSFileConstantsService providing OS.Consts.LIBC. The constants from
OS.Consts.Win have been inlined into subprocess_shared_win.js, since it was
already defining several other constants and it was the only consumer.
Differential Revision: https://phabricator.services.mozilla.com/D180358
This method returns a flat list of all the rules in a given stylesheet.
This will be helpful for DevTools so we don't have to recursively walk through
all the children rules (which is slow on the JS DevTools server).
Differential Revision: https://phabricator.services.mozilla.com/D181505
Add a chrome-only method for ending a wheel event group. This can then
be used by the webdriver to ensure that the wheel event group does not
live longer than the action chain.
Differential Revision: https://phabricator.services.mozilla.com/D177923
The tree devtools uses is the light dom + pseudo-elements + NAC, but sometimes
it wants to know stuff about the flat tree like assigned nodes. Previously it
was using a weird mix of the anonymous vs. non-anonymous walkers to get what it
wants, but that's needlessly complicated.
Instead, make InspectorUtils.getChildrenForNode do the right thing, and add
assigned nodes explicitly.
While _getChildren using a walker might seem like a good idea for performance,
realistically it was using InspectorUtils under the hood, and this is much
simpler.
Differential Revision: https://phabricator.services.mozilla.com/D174491
This doesn't help know what particular resource DevTools is currently inspecting,
but at least it helps know if it debugs something:
* one or many BrowsingContext(s) for regular DevTools (you can use BrowsingContext.watchedByDevTools instead)
* the whole process for the Browser Console/Toolbox
Differential Revision: https://phabricator.services.mozilla.com/D173295
This doesn't help know what particular resource DevTools is currently inspecting,
but at least it helps know if it debugs something:
* one or many BrowsingContext(s) for regular DevTools (you can use BrowsingContext.watchedByDevTools instead)
* the whole process for the Browser Console/Toolbox
Differential Revision: https://phabricator.services.mozilla.com/D173295
Add activeSessionHistoryEntry attribute to CanonicalBrowsingContext to
expose the existing implementation of
CanonicalBrowsingContext::GetActiveSessionHistoryEntry.
Differential Revision: https://phabricator.services.mozilla.com/D173235
Add activeSessionHistoryEntry attribute to CanonicalBrowsingContext to
expose the existing implementation of
CanonicalBrowsingContext::GetActiveSessionHistoryEntry.
Differential Revision: https://phabricator.services.mozilla.com/D173235
This makes various changes to the named lookup/navigation code to make
them more precise, and avoid issues which could happen if a window is
closed while script is still executing.
This also should improve handling for inactive windows in some cases, by
more frequently working off of the WindowContext tree rather than the
BrowsingContext tree.
As part of these changes, some behaviour was changed around e.g. the
file URI exception to avoid the deprecated nsIPrincipal::GetURI method.
I don't believe the behaviour should have changed in a meaningful way.
Differential Revision: https://phabricator.services.mozilla.com/D171755