Some events that actors need to listen to are chrome events which are not received by the listener in the window (even with mozSystemGroup = true).
Differential Revision: https://phabricator.services.mozilla.com/D8014
--HG--
extra : moz-landing-system : lando
This patch adds a messaging mechanism to actors that work like this:
If browser.fission.simulate is true, messages handled by ActorManagerChild will only be dispatched to an actor tied to a specific frame, specified either by its frameId (outerWindowId) or by its browsingContextId. Messages that lack the information about the destination frame will be considered meant for the top-level frame.
In addition, a sendMessage API is added to ActorChild that automatically adds the id information to the outbound message, making it easier for it to be handled in the parent.
The frameId support is to ease the transition of some code that is already using outerWindowIds. For new code, it is preferred to use the browsing context ids, together with bug 1496840
Differential Revision: https://phabricator.services.mozilla.com/D7933
--HG--
extra : moz-landing-system : lando
This fixes the addEventListener in ActorChild that I got wrong on bug 1490810, as it was still directly adding the events to the message manager, instead of going through the dispatcher (which can simulate the Fission process boundaries). ActorChild.addEventListener is meant for actors to add more events after they are constructed (that were not declared in nsBrowserGlue or ActorManagerParent)
Differential Revision: https://phabricator.services.mozilla.com/D7932
--HG--
extra : moz-landing-system : lando
Using a startup timeout of 0s should always cause an IOError,
even for builds which startup within 100ms (pgo, Nightly opt).
Further the test should not modify the internal startup timeout
property, but pass the timeout as parameter to "start_session()".
Differential Revision: https://phabricator.services.mozilla.com/D10224
--HG--
extra : moz-landing-system : lando
When the touch similation is enabled on RDM, TOUCHEVENTS_OVERRIDE_ENABLED is
propagated to all descendants docShells, so that we can just query it and return
PointerCapabilities::Coarse for the case.
Differential Revision: https://phabricator.services.mozilla.com/D10203
--HG--
extra : moz-landing-system : lando
We finally updated our host utils at some point after bug 1431533, so this
works now.
robocop_head.js is being included as a normal page <script> as well, though, and
as such is left to bug 1502674.
Differential Revision: https://phabricator.services.mozilla.com/D10278
--HG--
extra : moz-landing-system : lando
Extension start-up is blocked on receiving an initialization message
from the extension child process. If the extension browser goes away
before a response is received (e.g. if the extension is crashed), stop
waiting to avoid blocking the startup (and shutdown) forever.
This is not the cause of bug 1501375, but still worth fixing
( for bug 1355239 ).
Differential Revision: https://phabricator.services.mozilla.com/D9959
--HG--
extra : moz-landing-system : lando
Make off-thread and main-thread parsing more consistent by using the
JSContext tempLifoAlloc always. This also makes BytecodeCompiler APIs
more consistent.
Remove BytecodeCompiler::alloc which was obscuring lifetimes and
conflicts of allocator.
Differential Revision: https://phabricator.services.mozilla.com/D9978
--HG--
extra : moz-landing-system : lando
Move LifoAllocScope out of BytecodeParser to avoid ordering issues that
may arise when LifoAllocScope is wrapped.
Differential Revision: https://phabricator.services.mozilla.com/D9977
--HG--
extra : moz-landing-system : lando
Directly construct a LifoAllocScope on cx->tempLifoAlloc inside
RegExpObject::create. The data allocated temporarily does not outlive
this function. Also simplify callers as a result.
Differential Revision: https://phabricator.services.mozilla.com/D9976
--HG--
extra : moz-landing-system : lando
This isn't strictly part of removing support for non-restartless
extensions, but it ensures that sync is testing with the types of
extensions that people are really using these days.
Differential Revision: https://phabricator.services.mozilla.com/D10111
--HG--
extra : rebase_source : 9737bdce09464d7efb6150c15b1936bac99278f9
extra : source : 05f4f82cd81ced4c8cd441e7af0a31b728287bf1
After bug 1496622, the IDL parser converts some references to `nsresult` in IDL files to `::nserror::nsresult` in IDL-generated Rust files. But it doesn't convert others. It should convert them all consistently, and this patch makes it do so by adding conversion of the return type of attribute getters/setters and references generated by the IDL parser's Typedef class.
MozReview-Commit-ID: 838K8XGjvTx
Differential Revision: https://phabricator.services.mozilla.com/D10121
--HG--
extra : moz-landing-system : lando
- Make ServiceWorkerGlobalScope.importScripts() throw a NetworkError when receiving a
bad (i.e. non-JavaScript) MIME type
- Correct registration-tests-mime-types.js to expect TypeError when registering
a service worker that calls importScripts() with a bad MIME type, per spec
- Add WPT import-scripts-mime-types.https.html to test importScripts success/failure,
depending on MIME type
Depends on D6416
Differential Revision: https://phabricator.services.mozilla.com/D9886
--HG--
extra : moz-landing-system : lando
- Change "ServiceWorkerRegisterMimeTypeError" to "ServiceWorkerRegisterMimeTypeError2"
to account for more acceptable MIME types
Differential Revision: https://phabricator.services.mozilla.com/D6416
--HG--
extra : moz-landing-system : lando
Remove the keepUntil menulist and label, add a checkbox that toggles the value of 'network.cookie.lifetimePolicy' between 2 and 0.
Differential Revision: https://phabricator.services.mozilla.com/D9955
--HG--
extra : moz-landing-system : lando
In original design, payment method response data is passed between processes
through a simple nsString. It means a special encoder/decoder is needed for
special response data, ex. BasicCardResponse, to serialize/deserialize
into/from the nsString. However, when a token spliter, ':', ';' and '@', is
used in response data, it makes the encoder/decoder can not work normally.
It is hard to define a suitable token spliter set for encoder/decoder.
So instead of using an error-prone encoder/decoder, this patch defining a new
IPC structure for response data.
--HG--
extra : rebase_source : 4972033516bc861ea3f975a27b7688fc6eb89a94
Needed to allow localizers more control over what needs to be translated in a
String that contains another already translated String that should be bolded.
Differential Revision: https://phabricator.services.mozilla.com/D9629
--HG--
extra : moz-landing-system : lando
Removing unused CTA layouts from multivariant testing for Pocket users without the mobile app installed.
Differential Revision: https://phabricator.services.mozilla.com/D9858
--HG--
rename : browser/components/pocket/content/panels/tmpl/ho2/ho2_sharebutton_v2.handlebars => browser/components/pocket/content/panels/tmpl/ho2/ho2_sharebutton.handlebars
extra : moz-landing-system : lando