This adds a new coarse-grained whitelisting function, whose usage should be kept to a minimum but is necessary because many mochitests have cleanup issues on shutdown.
The module now handles cases that only happen in mochitests, where rejections can occur in contexts that are unloaded and more than one test file can be executed sequentially in the same process.
MozReview-Commit-ID: 8xejMxoSBzf
--HG--
extra : rebase_source : 67219bd686d43199ab10652e6ee1fda8ee1a2d1a
extra : source : 22e7144f857ce6a49764375f1e5ddf3e1ead7a96
This adds a new coarse-grained whitelisting function, whose usage should be kept to a minimum but is necessary because many mochitests have cleanup issues on shutdown.
The module now handles cases that only happen in mochitests, where rejections can occur in contexts that are unloaded and more than one test file can be executed sequentially in the same process.
MozReview-Commit-ID: 8xejMxoSBzf
--HG--
extra : rebase_source : de5fa91a5e9769c7ca42fc2c00ea54f169a3e12b
This removes nearly half of the time spent in the child process pause in
bug 1118086. (On my laptop, it cuts the child process pause from about
1560ms to 860ms; the parent process pause is still just over 5 seconds.)
Using querySelectorAll to find only the options that need to be locked
is much faster than iterating over them and locking all of them both
because the iteration is slow and the locking is somewhat slow even when
it's a no-op.
MozReview-Commit-ID: 17h3WIt9c2O
--HG--
extra : transplant_source : %A2H%DC%8A%CF%CFI%B0%D5%D2%05%1B6%B6%B1o%89%98D%1B
Right now, app menu doorhangers/badges have their state managed
directly inside panelUI.js. This is problematic because these
doorhangers and badges usually have to do with Firefox itself,
and not the specific window that's showing them. Accordingly, the
simplest solution was to move panelUI.js's notification state out
into a jsm file, which will fire notifications that all panelUI
instances can listen to.
MozReview-Commit-ID: 7b8w1WsQ29p
--HG--
extra : rebase_source : 23575df8176b862ec0e6a039173b105c45c76de9
AddonConstants duplicated AppConstants, but having it just include
the build-time constants meant that the logic for whether to enforce
signing was repeated in a few places (and it was incorrect in
the front-end code!). Now we centralize that logic in AddonSettings.jsm
MozReview-Commit-ID: 2f4x9fnUpPs
--HG--
extra : source : a589b98517d5fc6fe1704f752a7eb2984d18b3ac
When upgrading an old profile that still uses "downloads.sqlite", information about in-progress and paused downloads will be lost. The history of completed downloads will be preserved because it is stored in the Places database, although it may be affected by history expiration.
MozReview-Commit-ID: GFqvACKC4E1
--HG--
extra : source : 63d49c2d1fd68be15e295b90e9f0c98170158466
Remove suggested and enhanced tiles along with related campaign, frequency-cap, inadjacency, pings, preferences, strings, styles, tests.
MozReview-Commit-ID: FkjaSpSFQHu
--HG--
extra : rebase_source : 1c58ac542180f0abb290639ec1c61b9edf3d0a51
Since the order of events is 'blur' followed by 'focus', we send a message from the content process to the parent process and wait for a reply to give enough time for the parent process to signal that the 'blur' was related to the focusing of the search field. If the parent process hasn't signaled as such, then the content process will proceed with hiding the dropdown.
MozReview-Commit-ID: 6ngoo9uHcsM
--HG--
extra : rebase_source : caf43a975827aec71ba82fe39435b05c954673bc
