Capturing the viewport of a ChromeWindow does not make sense
because ChromeWindows do not normally have a scrollable area.
test_capture_viewport loads an HTML document to "get scrollbars", but
scrollbars and indeed HTML documents make no sense in ChromeWindows.
The viewport is really only a concept in web content.
As if this is not bad enough, when window.openDialog is called on
a ChromeWindow Marionette also fails to load the content frame script.
MozReview-Commit-ID: 7XXD45qIGim
--HG--
extra : rebase_source : 9d0ab36d1f04dbc5b3cb7f1e29ff4b8adb07481d
When the Gecko Profiler runs, we keep samples and markers for threads in
some occasions (eg when a Worker ends). But we fail to account for the
case where these threads have output no sample and no marker yet.
MozReview-Commit-ID: 2IEghD0v5Qd
--HG--
extra : rebase_source : b1af41c2d24b92c278922940151093f8b7d197db
The test needed to be rewritten as we can't have the 3 warning messages
at the same time (see https://hg.mozilla.org/mozilla-central/rev/084f217c4d49#l1.76
and https://hg.mozilla.org/mozilla-central/diff/817eb00ba702/toolkit/components/passwordmgr/InsecurePasswordUtils.jsm#l1.106).
This wasn't picked up by the old frontend test because it is disabled.
In order to test the different warning messages we open 3 different pages
which log the appropriate warning.
MozReview-Commit-ID: Gqa8GrMh8iR
--HG--
rename : devtools/client/webconsole/new-console-output/test/mochitest/test-iframe-762593-insecure-form-action.html => devtools/client/webconsole/new-console-output/test/mochitest/test-iframe-insecure-form-action.html
rename : devtools/client/webconsole/new-console-output/test/mochitest/test-iframe-762593-insecure-frame.html => devtools/client/webconsole/new-console-output/test/mochitest/test-insecure-frame.html
rename : devtools/client/webconsole/new-console-output/test/mochitest/test-bug-762593-insecure-passwords-web-console-warning.html => devtools/client/webconsole/new-console-output/test/mochitest/test-insecure-passwords-web-console-warning.html
extra : rebase_source : 2afb77cb3dcf0f8df5116b7e7d85030a52bc0bc2
When we branched to beta, the MinGW build started failing with a strange error
like "could not find the robustcheckout Mercurial extension". We disabled it
for a while, but now we're re-enabling it (and fixing the problem.)
The root culprit of this was that we were using the incorrect mozconfig. MinGW
does all sorts of stuff in the mozconfig, but the beta branch overrides the
mozconfig using platform_overrides in
testing/mozharness/configs/builds/branch_specifics.py
We avoid this override by changing the MinGW platform so it doesn't match
and the mozconfig doesn't get overridden.
MozReview-Commit-ID: JkETWCRHacO
--HG--
extra : rebase_source : 5ef7d96804acd3a4eaa6dd6cc8b483f3de438b61
This method is used to replace some GetNativePath usage for logging.
MozReview-Commit-ID: 9nWf2r4oviA
--HG--
extra : rebase_source : b58e45ab38621179cd802979131fdddbfe65079e
extra : intermediate-source : b4ded2247082f98fe18eb640c5fafeb9bc107ac0
extra : source : 21a82c1faeffc7c0d7b3a5ef0ae4c5243c81a586
This removes the gyp files to build webrtc. It looks like part of Bug 1371485 is
to vendor gyp elsewhere in tree at which time we can complete cleaning this up.
MozReview-Commit-ID: 8MqatafniN5
--HG--
extra : rebase_source : 1cf7a41f0b8a1a95dc008f4a39536ee7e76027c4
This method is used by some subsequent patches when unique opaque identifiers are necessary.
MozReview-Commit-ID: AreqK4MHdJP
--HG--
extra : rebase_source : d5b85c2c9212618f54a6ac2f5199651b01c99510
extra : intermediate-source : 67c3c7a1012b9fdd628928bec61472c6ce580616
extra : source : c9a67330c600dbe454fd2ce5025247171e0c0e22
Currently only |value_type| is implemented.
MozReview-Commit-ID: 1mejzvkuako
--HG--
extra : rebase_source : 69e08073adbb9a866db26e515702a0659ece0a70
extra : intermediate-source : 3696381ddfdc19ab2f901ca4247e1cb4efb27731
extra : source : 35d760da1d73dd51614f434c26e5ce80ff690829
It was only used in the 55 Nightly and never meant to stay around.
MozReview-Commit-ID: JDJr9WC4V5M
--HG--
extra : rebase_source : af52eb24c4d599651a4cbde7b00049272448c9e6
Change the order of the icons so it makes more sense.
Use te same 'jump to debugger' icon as in the console.
Add expanded/collapsed icon on event listener definition.
MozReview-Commit-ID: 33tt7VX32NH
--HG--
extra : rebase_source : 58b2fd2e4dd140b886ce9e7dc5dd55485c8eacd4
We extract the ARM disassembler bits and place them in
jit/shared/Disassembler-shared.{cpp,h}, and then clean them up and
generalize them. The ARM assembler is slightly modified to deal with
this but the changes are local.
We then add code to the ARM64 assembler to drive the disassembler.
The structure is as for the ARM disassembler.
--HG--
extra : rebase_source : 7197ec8b3b8985005efb7522b6719140b2eac5e4
extra : source : aa8517d9efb1aa89f4661bdb095d5a0f526cb652
This adds support for detecting globals created by these helpers, as well as a
rule to enforce their use over the older XPConnect variants.
The latter rule also supports fixing code to use the newer variants, and will
be used in the next part to rewrite in-tree ESLint-enabled code that fails it.
MozReview-Commit-ID: 6Bgo6ohQA5j
--HG--
extra : rebase_source : feca0a0ed339420ea19faa1f6614e6253f0c840e
extra : absorb_source : d32d3d23fbd2c7dcae082375a1f9a61766b04b75
extra : histedit_source : 83cebb4f3eb66a79d38ee5412a5739d0c603425b
This is necessary before we enable the ESLint rule to require using
ChromeUtils for module imports rather than older methods.
MozReview-Commit-ID: mKqByUS0o2
--HG--
extra : rebase_source : d4b856aac7ff7eddc37cbf591c4e6522c45453e2
extra : histedit_source : 1ca2b6031e480fb44a15991241901224acc9e52f
This helper makes it easy to lazily import a JavaScript module the first time
one of its exports is required. It is intended to replace
XPCOMUtils.defineLazyModuleGetter, which has similar functionality but is much
less efficient.
MozReview-Commit-ID: 2zxXYwrn3Dr
--HG--
extra : rebase_source : 998de7388ee03fdec0a0949b4e43bd9169dbb592
extra : histedit_source : 414d0ed1842b2270146d37b2788a56c682d3d695
Looking up and copying exported properties each time a module is loaded is
fairly expensive at the best of times. It's even more expensive when we only
want to export a subset of symbols, which generally requires creating a
temporary object to hold the exports, or fetching them directly from the
returned global.
Aside from making the general case a bit faster, storing exports on an object
allows us to optimize lazy module imports by fetching imported symbols
directly from the exports object with very little additional overhead.
MozReview-Commit-ID: C9PGoXPNmsh
--HG--
extra : rebase_source : 6232cf7a52fd69ebeb8b6e39680646f287c272a8
extra : histedit_source : b223c73a6e9092491f4fb09f8c795f5aa4b43df3
The shutdown path has a way to free the sObjectMap before all plugin references to it have been executed. It does this by scheduling a DeferNPObjectReleaseRunnable, then shutting down the plugin with PluginInstanceChild::Destroy. This patch keeps the runnable from failing in that case.
Various updates to emulator command lines. Use -skip-adb-auth. Use -verbose
instead of trying to specify debug categories. Use more -memory and -cores
where applicable. Use -ranchu and -selinux permissive where applicable.
