This leaves the AsyncOpenFinal function because it is
used for Socket Process launch.
It adds some includes to fix Unified Builds.
Differential Revision: https://phabricator.services.mozilla.com/D119638
Originally these includes were wrapped in an ACCESSIBILITY define because the
bug that manifested only affected screen readers. However, theoretically
speaking other things *could* cause us to initialize COM early and run into
troubles, so this is not *strictly* an a11y issue from that perspective. It
wasn't wrapped around ACCESSIBILITY defines inside PreXULSkeletonUI.cpp for
this reason, but there was still lingering inconsistency inside the moz.build
file. This corrects that.
Differential Revision: https://phabricator.services.mozilla.com/D119541
This is to allow "max difference: 1, number of differing pixels: 41". The
differing pixels are all antialiased fringe along the curved edges of the
test's radio-buttons.
Differential Revision: https://phabricator.services.mozilla.com/D119778
The update-verify-next test is new in Thunderbird 91. Since Thunderbird versions
do not include the esr suffix, a separate regex is needed.
Differential Revision: https://phabricator.services.mozilla.com/D119890
This patch fixes the intermittent failures being triggered by test_ext_webrequest_auth.html by making sure that
the "http-on-modify-request" observers added by the test tasks part of this test file are going to ignore any http
request that isn't related to the mochi.test url that is expected to trigger the authentication dialog.
With the previous version of the chrome script executed by these two test tasks, there was a chance that the observer
would be setting the mocked nsIAuthPromptProvider/nsIauthPromp2 notification callback on the wrong channel, if
the http channel was also related to the mochi.test host. After that the observer was removed and it would not be
setting the notificationCallbacks on the channel that was meant to set it on (and that would make the testcase to
trigger the actual authentication prompt that can be seen in the failure screenshots).
As part of this patch we are also reverting the additional debugging logs added in a previous patch attached to
this issue.
Differential Revision: https://phabricator.services.mozilla.com/D119880
Depends on D119610. After fixing the error with targetList.destructor, calling CDP::stop() without having called CDP::start() before will trigger another failure.
This is because it will trigger a late load of RecommendedPreferences which will try to automatically initialize preferences
As we discussed about moving the init to be only performed during a call to applyPreferences, I am doing this change here to avoid the error.
This will not yet allow to call this from BiDi, or it would have to call it with an empty `preferences` map.
Differential Revision: https://phabricator.services.mozilla.com/D119611
* Removes the fallback to the old sent-tab
* Deletes the api to send URIs using commands
* Modifies tests that depended on that api to now use
other commands, namely the wipeEngine command
Differential Revision: https://phabricator.services.mozilla.com/D118086
When form autofill determines which extra fields were not autofilled, there is a chance that the filtered element will not have a value property (in our case, fieldset elements).
By ensuring we return an undefined instead of accessing a property that doesn't exist, we can ensure the rest of the credit card show panel flow works as expected
Differential Revision: https://phabricator.services.mozilla.com/D119660
Previously only the value in the parent process,
`windowGlobalParent.isInitialDocument`, was exposed to chrome JS. for testing
and other purposes, it is also useful to be able to read this value from JS in
a child process.
Depends on D119815
Differential Revision: https://phabricator.services.mozilla.com/D119816
This makes sure to clear and set the value more consistently when replacing
documents within a WindowGlobal, and makes sure to include the relevant flag in
the initializer.
In addition, the place where the flag is set is moved ahead to happen before
the call to `Embed` so that the information is ready before the window is
created.
Differential Revision: https://phabricator.services.mozilla.com/D119815
The update-verify-next test is new in Thunderbird 91. Since Thunderbird versions
do not include the esr suffix, a separate regex is needed.
Differential Revision: https://phabricator.services.mozilla.com/D119890
This patch include a small change to ServiceWorkerManager::StoreRegistration which does early exist
and not store the registration on disk if:
- the principal is from a WebExtension
- the addon is not enabled (or was already uninstalled) by the time we got to store the registration
- the addon is temporarily installed
At the moment it should not happen, but if ServiceWorkerManager::StoreRegistration was reached too late
for some reason and the registration was meant to be stored, the service worker would still be registered
again when the addon is started again on the next browser startup and stored on disk if it was meant to.
Depends on D119529
Differential Revision: https://phabricator.services.mozilla.com/D119530
This patch adds a new `temporarilyInstalled` property to the WebExtensionPolicy object, set to
the value of the same property from a Extension.jsm perspective.
The new property is being introduced mainly to be used in a patch that follows to allow the
ServiceWorkerManager internals to access that from the C++ layer (but it may be also
become a useful knowledge for other C++ components in the future).
Differential Revision: https://phabricator.services.mozilla.com/D119529
Worker targets only set threadActor late, quite asynchronously.
So that the target is registered in TargetCommand, but we can't call target.getFront
without having it to throw.
Differential Revision: https://phabricator.services.mozilla.com/D119672
