This function makes it possible to listen for multiple events from the
content process, even when there are frameloader swaps.
This commit also adds a checkFn param to firstBrowserLoaded, which is
useful.
MozReview-Commit-ID: 93ItHIPSGVU
Currently the e10s tab switcher doesn't set the primary="true"
attribute on a browser element until the tab switcher is
destroyed. This means that using the |content| global is unreliable in
e10s since it may take as long as the tab switcher's unload delay
before the attribute changes. Normally this doesn't matter since
|content| isn't useful in e10s. However, tests that use tabs like
about:preferences rely on |content|, and there isn't a good reason to
fix them. So let's just change the attribute immediately upon changing
tabs.
MozReview-Commit-ID: 1cgJbmXD6of
Currently, if you try to use contentDocumentAsCPOW, you'll get an
exception saying that browser code is not allowed to use CPOWs. That's
because we cleverly tried to get the CPOW via
contentWindowAsCPOW.document. However, this property access happens
inside remote-browser.xul, where CPOWs are forbidden. So it doesn't
work.
MozReview-Commit-ID: ANWad4tvGpU
When we resume a download, the request referrer will be computed again
with default referrer policy (which is wrong in the cross-origin case)
We should compute the request referrer before calling download API,
store it in download object and not try to compute again (using
REFERRER_POLICY_UNSAFE_URL).
MozReview-Commit-ID: JhHcljfN0Ne
--HG--
extra : rebase_source : 135e4d5e506d165f9cf14253ed1ab684e7dcebe3
Nothing significant in this release, just to be in sync with upstream
MozReview-Commit-ID: GOMzG6TOHYg
--HG--
extra : rebase_source : 73c7a83e358d0b8c7686f0b79d805947c928600e
Summary:
I always need to remember to exclude it from my patches, and it's the
main reason I don't use phabricator.
It is harmless to anything other than arcanist, so there's no reason to not
check it in, I'd say.
Reviewers: dkl
Reviewed By: dkl
Bug #: 1424257
Differential Revision: https://phabricator.services.mozilla.com/D330
MozReview-Commit-ID: 8uE9ac3uS4y
The service worker job queue can get stuck sometimes, so we don't want
the per-process service worker data structure to hold strong
references to content. Instead, I add a proxy that is only a weak
reference. The wrinkle is that we need to keep the promise alive as
long as the job and the window are otherwise alive. I solve this by
putting a cycle collected reference to the promise on the window
itself.
MozReview-Commit-ID: GbmCY4ZIQWk
--HG--
extra : rebase_source : 363ea865fd51bb44f3e727cd3469e316370e7cbc
Initial support for CSS variable tooltip. Removed title attribute from
variables and added a new tooltip displaying the same content.
MozReview-Commit-ID: FeHmgiS7KQj
Summary: We can probably abstract more stuff in the future, but this seems like a good start.
Reviewers: jcj
Reviewed By: jcj
Bug #: 1396907
Differential Revision: https://phabricator.services.mozilla.com/D323
Since the sidebar menu is the only element using the small checkbox style, this is re-implemented placing the styles closer to the existing ones that are required for the checkbox to work. Some descendant selectors can be removed in the process.
MozReview-Commit-ID: vcVvvkvNeA
--HG--
extra : rebase_source : 6ff608c31c311688ea7caf37976bb38d977b7875
On most platforms we have some platform-dependent registers that are
used for specific purposes. These need to be wrapped in the type-safe
register wrappers. This patch factors that wrapping into a
SpecificRegs struct that is defined per-platform and included in
BaseCompiler. This moves platform dependencies out of BaseCompiler
and toward the top of the file, where they belong.
Also, I took the opportunity to further clean up some ifdefs and
document how I use JS_64BIT vs JS_PUNBOX64.
MozReview-Commit-ID: F0vOnQp01In
--HG--
extra : rebase_source : 69042aae4b7f6612d5d9e5d6c37327eabafa6d1d
extra : source : 590bd3618081d312f1aceca22680715498a037db
The idea here is that on quite a few platforms we will not necessarily
want to use the assembler's ScratchRegisterScope (for any type),
because the assembler uses its scratch registers very actively, as
does rabaldr. So on those platforms we want our own. Same on x86,
where there isn't a scratch register.
Anyhow, to make that happen we generalize the scratch register
management here so that it can use the platform's when that is
appropriate (x64 for all, x86 for float registers) and have its own
when that is appropriate (most other platforms). This is managed with
ifdefs set up in the configuration section.
The net result is fewer, and more easily managed, platform
dependencies.
MozReview-Commit-ID: AOpu7ju4t1c
--HG--
extra : rebase_source : 5d1d4f1f925d61be5e753209f17e5c8b420dcd5f
extra : intermediate-source : 7cea7f8e7d0b5eb0109c431d35c26cdf0ae24330
extra : source : 4a77af46bd0e620076e5b646f752bab9643ea29f