"async" methods defined in scripts loaded via a <script> tag seem
to indirectly use the document's Promise, which is not usable after
the DOM of the document has been destroyed.
This is an issue if we invoke this code during the destroy of the
toolbox.
MozReview-Commit-ID: C8juQqJlVDN
--HG--
extra : rebase_source : 1d30dd878721119064081dfa33881488f7600a4b
Remove check for background-sensor permission, since there is no place
in the code that grants that permission anymore.
MozReview-Commit-ID: 6im17gfzmGi
--HG--
extra : rebase_source : 149f0d32e46c7fdb6839cdb574265d976917717c
Vibration is the last user of permissions helper functions in
navigation, these can be simplified into the vibrate functionality.
MozReview-Commit-ID: CGA5WL7nObS
--HG--
extra : rebase_source : bdab714b0bd3a5774300ad71c07090a9565b75ea
There is at least one reference to the MediaManagerService being used within
mobile in conjunction with WebRTC, so we should do the same thing that desktop
Firefox is doing here.
MozReview-Commit-ID: 1z1cLapxK2F
--HG--
extra : rebase_source : cea422e1bce709001d2af673c6f3d3fd71ebc810
This is a straight copy-and-paste of the non-range-based desktop code in Sanitizer.jsm.
MozReview-Commit-ID: 71r8LO4xzYF
--HG--
extra : rebase_source : 276cb7d1043016f3df04727bd8437e9e014a558e
The OfflineAppCacheHelper was apparently introduced after the Sanitizer had been
forked for Fennec and so far nobody bothered to use it there as well.
MozReview-Commit-ID: 42Uk5hfvf9y
--HG--
rename : browser/modules/offlineAppCache.jsm => toolkit/modules/offlineAppCache.jsm
extra : rebase_source : 77e542dbbdfea62b918b89b4c0799be7e3f89ef9
Update existing multiline debug lines to use the new format.
MozReview-Commit-ID: 3mkEAlgSePp
--HG--
extra : rebase_source : 3589f6de9b7ff1b8ef18904f41d7f262908d91ef
Add some eslint rules to prevent mistakes and help correct debug/warn
usage.
* Make sure debug/warn are used with template literals.
* Make sure debug/warn are used with single template literal instead of
concatenated expressions.
* Make sure debug/warn literals don't include unnecessary JSON.stringify
calls.
MozReview-Commit-ID: LOLYbwIxGuf
--HG--
extra : rebase_source : 013281c1ddbb773c2b2b852f6d5d2006c29344de
Coalesce multiple lines into one line when logging, so that long lines
can be split into multiple lines. For example,
debug `foo=${foo}
bar=${bar}`
To actually log multiple lines, use multiple log calls,
debug `foo=${foo}`
debug `bar=${bar}`
MozReview-Commit-ID: 2Wedxkxccm8
--HG--
extra : rebase_source : 7290cc0df5d25bec660d51051a8a7bb21d814178
These functions cause main-thread certificate verifications, which is bad for
performance. In general, nsIX509CertDB.asyncVerifyCertAtTime should be used
instead.
MozReview-Commit-ID: 9nkUDmyFY0k
--HG--
extra : rebase_source : d3e8a02e2d21e5507e71681b88f0360edf64b790
Rather than recording how many leaked (ghost) windows we see at
various times, I think it will be more useful over all to record what
the maximum number of ghost windows we see during a single
ping. Hopefully this will show up in a way that generates automated
alerts better than GHOST_WINDOWS.
If this works out, I'll make this telemetry measure permanent and
remove GHOST_WINDOWS.
MozReview-Commit-ID: 11ma1lLGz5L
--HG--
extra : rebase_source : dc7705d288d3301fc0a1ec15f8dadfb66fe8820f
All the upstream issues have been resolved, so this now works well.
There is minor artifacting on the linux CI which does show up on
all platforms in my local testing, but it's too minor for more
effort to go into this. I get perfect results locally, so needs
the full fuzzing range.
MozReview-Commit-ID: 8XZk85kn9WP
--HG--
extra : rebase_source : d337b185d83be5fa591f21848e2ce6b8cf0a462c
This has a big performance impact because we instead of defaulting to the bounds
of the image we can use a much smaller temporary surface.
--HG--
extra : rebase_source : 0daba1adae742df3b983f80944dc4344bc70a5d6
The argument is never used in the local file copying function. So let's
nuke the argument.
MozReview-Commit-ID: JeU4LaVvGD7
--HG--
extra : rebase_source : 0e305c5bff0e3871fd11a554d75e7f53ceea4bdd
This was only used for the remote server case. That code was recently
deleted.
MozReview-Commit-ID: 7usqWZ7CuBR
--HG--
extra : rebase_source : f27b37391802a2980feffa5d88c92228d137824f
extra : source : 46b8a00288c8d7b88fd9b7aee20e88ddfd96d57b
With the transition to Taskcluster, "uploads" are artifacts in a local
directory. So we don't need to support uploading to a remote server
using SCP.
This commit removes all the code to support uploading to a remote
server.
And since property files were only written out for the remote case, all
that code can be deleted as well.
Since UPLOAD_HOST no longer means anything, we no longer set it in
mozharness configs.
MozReview-Commit-ID: 66gkM8erkGk
--HG--
extra : rebase_source : ee85bb927cfb98e1ca383ab2591febfc1f0ce5cd
