To avoid crashing in macOS 10.15, allow access to the proc_info PROC_INFO_CALL_SETCONTROL syscall variant in the GMP and RDD sandboxes.
Differential Revision: https://phabricator.services.mozilla.com/D39079
--HG--
extra : moz-landing-system : lando
nsIX509CertDB::PrivilegedPackageRoot was added in bug 1178518 to support privileged packaged apps for Firefox OS. However, we no longer need to support this use-case.
Differential Revision: https://phabricator.services.mozilla.com/D38655
--HG--
extra : moz-landing-system : lando
This paves the way for us to use a dispatcher other than mDispatcher,
which will be useful in the MozPromise integration in the coming
patches.
Differential Revision: https://phabricator.services.mozilla.com/D39090
--HG--
extra : moz-landing-system : lando
Streamlined ifdefs by removing the remaining instances of PREF_VALUE. Also, changed media.eme.enabled to benefit from IS_NIGHTLY_BUILD, and removed duplicate logic in media.rdd-vorbis.enabled.
Differential Revision: https://phabricator.services.mozilla.com/D38952
--HG--
extra : moz-landing-system : lando
Defines and uses constants for patterns that commonly recur in StaticPrefList.yaml, such as #ifdef NIGHTLY_BUILD
Differential Revision: https://phabricator.services.mozilla.com/D38948
--HG--
extra : moz-landing-system : lando
Updated repetitive #ifdef RELEASE_OR_BETA pattern to use the existing constant at the top of the file. Renamed NOT_IN_RELEASE_OR_BETA_VALUE to IS_NOT_RELEASE_OR_BETA, to follow naming conventions in child revisions.
Differential Revision: https://phabricator.services.mozilla.com/D38947
--HG--
extra : moz-landing-system : lando
This patch removes nsIClientAuthUserDecision and add another output parameter to nsIClientAuthDialogs.chooseCertificate.
Differential Revision: https://phabricator.services.mozilla.com/D38074
--HG--
extra : moz-landing-system : lando
As part of bug 1510569, the majority of the `nsIWebProgress` event listeners
have moved from the `WebProgressChild`/`RemoteWebProgress` to the
`BrowserChild`/`BrowserParent`. In responsive design mode, the
`RemoteWebProgress` previously would update the state of the `<iframe
mozbrowser>` with document URI and title which would be mirrored back to the
`<xul:browser>` when leaving RDM. However, the event handlers in the
`BrowserParent` call directly into the `<xul:browser>`, skipping the `<iframe
mozbrowser>` entirely. Therefore, when RDM is shut down, old state will be
mirroed to the `<xul:browser>`, leaving it in an inconsistent state. We now
mirror the state from the `<xul:browser>` to the `<iframe mozbrowser>` with an
`nsIWebProgressListener` so that the `<iframe mozbrowser>` will not clobber the
`<xul:browser>`'s state when leaving RDM.
Differential Revision: https://phabricator.services.mozilla.com/D38918
--HG--
extra : moz-landing-system : lando
When in responsive design mode, the `browser-child.js` script will be loaded by
the `<xul:browser>` in the parent process, where a `BrowserChild` does not
exist. Attempting to retrieve this from the `DocShell` will cause an error,
preventing the script from executing correctly. We now gracefully handle the
case where browser-child.js is loaded in the parent and no `BrowserChild`
exists.
Differential Revision: https://phabricator.services.mozilla.com/D38917
--HG--
extra : moz-landing-system : lando
The work from bug 1510569 that has ported the majority of the `nsIWebProgress`
event handlers from `WebProgressChild`/`RemoteWebProgress` to
`BrowserChild`/`BrowserParent` was not properly propogating the events in the
responsive design mode case. The `BrowserParent` assumed that its frame element
was an `nsIBrowser`, but in RDM it is an `<iframe mozbrowser>` which does not
implement `nsIBrowser`. In the RDM case we now walk up the document in the
`BrowserParent` tree to find the `<xul:browser>` and call the event handlers on
that instead.
Differential Revision: https://phabricator.services.mozilla.com/D38916
--HG--
extra : moz-landing-system : lando
test_bug819670_getter_throws.html:
Previously, the document context inspected in the console was the test
harness XULDocument, but now it will be an HTMLDocument. Update the
checks to make sure the inspected object has the same own properties as
the test documents own properties.
other tests:
Simply replace the expected document type.
Differential Revision: https://phabricator.services.mozilla.com/D38695
--HG--
extra : moz-landing-system : lando
Now that the functionality we we wanted to preserve has been moved out of
XULDocument, we can start loading XUL files as XHTML. This will allow
the removal of XULDocument once we are confident that everything is working
correctly as XHTML.
Differential Revision: https://phabricator.services.mozilla.com/D38694
--HG--
extra : moz-landing-system : lando
Adds a new pageload test that captures the "pagerendered" event from
PDF.js.
Differential Revision: https://phabricator.services.mozilla.com/D37935
--HG--
extra : moz-landing-system : lando