The return value from Cu.import() does not include lexically scoped
symbols so stop using it here. Also stop using Extension.generate()
while we're here.
MozReview-Commit-ID: HnX3RGgDHbR
--HG--
extra : rebase_source : b4e238f2a5f1c9dce838b4dd70447edd9f401c10
Fix get service with wrong interface name and a double init issue.
MozReview-Commit-ID: BA0wex06eWb
--HG--
extra : rebase_source : 0e32128c470ec9d116840a372ab0893d476aa543
Since bug 1377447 we use EnsurePresShellInitAndFrames for
FlushPendingNotification when textbox gets focused, and
EnsurePresShellInitAndFrames should not trigger any reflows. So in theory,
there is something causes a reflow that we could improve on other platforms.
MozReview-Commit-ID: FAcSZKrv0Fr
--HG--
extra : rebase_source : 727f9ec1803e7046429bc7cf419aed9e4631f971
The reflow was suppressed by bug 1414252, and the expected reflow
for other platforms was dropped in that bug.
MozReview-Commit-ID: HyYhvntOpGx
--HG--
extra : rebase_source : 956e71c28e3840c8fe39da1aea8b5ea2a06081f6
This seemed to be working before by a fluke:
> Before bug 1375870, _constructAfterChildren was getting called several times,
resulting in change events triggering updatePrivacyMicroControls repeatedly.
> updatePrivacyMicroControls was using the auto-private-browsing checkbox to
decide whether to disable and hide the checkmarks of the other checkboxes.
> After bug 1375870, at the point when updatePrivacyMicroControls is called,
the preference value has not yet propagated to the auto-private-browsing
checkbox, so uPMC doesn't work correctly and is not called again.
Solution: use the actual preference value in uPMC.
MozReview-Commit-ID: 2AhRQwkjH5Q
--HG--
extra : rebase_source : dfcea62d925d019b880e87bc0f1551e78d756e9e
See comment 12. There is no guarantee 'canplaythrough' will always fire when
download is slow. It should listen to 'suspend' which is fired when download
is stopped.
MozReview-Commit-ID: GFUtjBpsAcT
--HG--
extra : rebase_source : db343efc4ab7b6bd248fe0e6033affc050950d0e
With all of our builds in Taskcluster now, we should never be uploading
symbols from build tasks. Unfortunately Windows builds were still doing so.
This patch removes MOZ_AUTOMATION_UPLOAD_SYMBOLS from all the in-tree
mozconfigs and a few other places so that it should always default off
(per moz-automation.mk). The rest of the uploadsymbols bits will be
removed once Thunderbird fixes their automation.
This patch was mostly autogenerated by running:
rg --files-with-matches UPLOAD_SYMBOLS browser/config/mozconfigs/ mobile/android/config/mozconfigs/ | xargs sed -ri '/.*UPLOAD_SYMBOLS.*/d'
sed -ri '/.*UPLOAD_SYMBOLS.*/d' build/unix/mozconfig.linux build/mozconfig.win-common build/macosx/local-mozconfig.common build/mozconfig.automation
Then mobile/android/config/mozconfigs/common and
taskcluster/scripts/builder/build-linux.sh were hand-edited.
MozReview-Commit-ID: Cy8kSEodSg4
--HG--
extra : rebase_source : 01caf1651b4eb428313e1f371aa585f8f34c4151
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 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
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
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
MozReview-Commit-ID: 9c5Bp9V9Nl3
***
Bug 1400315- Fix padding and remove center alignment for empty downloads in downloads dropdown; r=sfoster
--HG--
extra : rebase_source : a525fa2367d188a1951fe92ab89e513fb27ff7aa