This ensures that we wait for the desired URL in the browserLoaded call, rather
than resolving the first-loaded one.
This also renames the file to make it more indicative of what it actually tests.
Differential Revision: https://phabricator.services.mozilla.com/D55045
--HG--
extra : moz-landing-system : lando
CacheEntry::GetAltDataSize() can throw an error if the size isn't known yet, i.e. when the output stream wasn't closed yet. nsHttpChannel::OpenCacheInputStream() doesn't check the return value and in case of failure uninitialized altDataSize is stored in mAltDataLength.
Differential Revision: https://phabricator.services.mozilla.com/D55085
--HG--
extra : moz-landing-system : lando
Some text in the toolbar wasn't properly vertically aligned in this interface.
Differential Revision: https://phabricator.services.mozilla.com/D54743
--HG--
extra : moz-landing-system : lando
The test is sometimes failing because there's a pending
connection to the server while the connection is closed.
My guess is that somehow the test could have been checking
other nodes instead of the current evaluated on to wait
for a node to be fully expanded.
The fix made here is to make sure that we only have one
node displayed when testing the object inspector.
Differential Revision: https://phabricator.services.mozilla.com/D54943
--HG--
extra : moz-landing-system : lando
And clean-up surrounding code by removing useless namespace qualification.
It seems like the first call to Broadcast is useless? Or am I missing something?
Differential Revision: https://phabricator.services.mozilla.com/D55000
--HG--
extra : moz-landing-system : lando
Right now it's enable but it throws with "remove() is not a function".
Depends on D55096
Differential Revision: https://phabricator.services.mozilla.com/D55097
--HG--
extra : moz-landing-system : lando
As they have an innerHTML property, and it is useful.
I didn't find relevant tests for this. browser_inspector-traversal.js tests only
the server bits.
Differential Revision: https://phabricator.services.mozilla.com/D54422
--HG--
extra : moz-landing-system : lando
BrowserTestUtils.crashFrame now accepts additional `options`, with an argument `crashType` that may
take "CRASH_OOM" or "CRASH_INVALID_POINTER_DEREF"|null to specify the nature of the crash. The names
are taken from CrashTestUtils.jsm but this module cannot be imported as such as it has non-trivial
binary dependencies.
Depends on D54130
Differential Revision: https://phabricator.services.mozilla.com/D54700
--HG--
extra : moz-landing-system : lando
We'll use this method to expose additional information to the front-end for recovering from OOM.
Differential Revision: https://phabricator.services.mozilla.com/D54129
--HG--
extra : moz-landing-system : lando
From extensive testing, it appears that the test fails (also on TV)
when one of the home pages is opened. This did not happen with
"about:robots". Apparently, a browser window leak can be observed if the
test starts at a homepage and opens another homepage tab in the test.
This patch works around the issue by initializing the window with about:blank.
Differential Revision: https://phabricator.services.mozilla.com/D55108
--HG--
extra : moz-landing-system : lando
This moves the Chromium remote debugging protocol implementation
in Firefox from using sessionstore-windows-restored to a new
remote-startup-requested notification observer.
This change makes it possible for applications to explicitly decide
at which stage it is considered safe to initialise the remote agent
listener. It is safe to emit this notification at any time since
the observer for it is only registered after the --remote-debugger
flag is is used.
The remote debugger only supports Firefox, so this patch does not
take care of GeckoView/Android.
Differential Revision: https://phabricator.services.mozilla.com/D54485
--HG--
extra : moz-landing-system : lando
This merges the previously two overlapping lists into one, with different classes to make obtaining the results easier.
As a side effect, preference based MozParams could now also be specified with a purpose.
Preference caching/observation to be added in the next changeset.
Differential Revision: https://phabricator.services.mozilla.com/D54898
--HG--
extra : moz-landing-system : lando
Bug 587780 originally added MozParam's purpose argument, at the time the default fallback was an empty string. This meant that to match only the default, purpose had to be defined as an empty string. In bug 1181645, the default purpose was changed to fallback to the string "searchbar", obsoleting the need for handling purpose as an empty string. However, the handling wasn't removed, making the code more complicated.
Differential Revision: https://phabricator.services.mozilla.com/D54897
--HG--
extra : moz-landing-system : lando