73c69599b3f12fa0f2dc45ee29fb202c93a9a695: Bug 1595985 - Add browser.urlbar.closeView webextension API. r=mak,mixedpuppy
Drew Willcoxon <adw@mozilla.com> - Wed, 13 Nov 2019 17:59:08 +0000 - rev 501818
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1595985 - Add browser.urlbar.closeView webextension API. r=mak,mixedpuppy This is based on D52612 Differential Revision: https://phabricator.services.mozilla.com/D52792
a65a260a14fe1950e0b061b12c62e55cea49df4a: Bug 1594735 - Upgrade android emulator used for x86_64 xpcshell tests; r=aerickson
Geoff Brown <gbrown@mozilla.com> - Wed, 13 Nov 2019 17:46:02 +0000 - rev 501817
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1594735 - Upgrade android emulator used for x86_64 xpcshell tests; r=aerickson Upgrade the emulator used by xpcshell tests to 29.2.1, the same version used by all other android tests. We have delayed this upgrade because of intermittent failures seen on the new emulator not seen previously - bug 1568063. After the packet.net upgrade to Ubuntu 18.04, try runs with the new emulator show that bug 1568063 persists but has less impact than the intermittent failures it resolves: More tests pass consistently with the new emulator than with the old. Differential Revision: https://phabricator.services.mozilla.com/D52851
25c597f8703fb05ceb531889a0a478bdebfd78fb: Bug 1594950 - Remove unused SurfaceRegistry API. r=jrmuizel
Markus Stange <mstange@themasta.com> - Wed, 13 Nov 2019 18:33:24 +0000 - rev 501816
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1594950 - Remove unused SurfaceRegistry API. r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D51758
4391cb16bb0b291b02a1fc42a7295c564d76d9ec: Bug 1594950 - Change NextSurface APIs to accept a dirty region, and remove the public method InvalidateRegionThroughoutSwapchain. r=jrmuizel
Markus Stange <mstange@themasta.com> - Wed, 13 Nov 2019 18:55:18 +0000 - rev 501815
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1594950 - Change NextSurface APIs to accept a dirty region, and remove the public method InvalidateRegionThroughoutSwapchain. r=jrmuizel Differential Revision: https://phabricator.services.mozilla.com/D50878
2a2c01a5ce9a25fd52d55b56a1b238eebfc7d752: Bug 1594950 - Track the nsChildView invalid region inside nsChildView, rather than on the layer. r=jrmuizel
Markus Stange <mstange@themasta.com> - Wed, 13 Nov 2019 18:33:20 +0000 - rev 501814
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1594950 - Track the nsChildView invalid region inside nsChildView, rather than on the layer. r=jrmuizel This allows us to move the call to InvalidateRegionThroughoutSwapchain to just before the call to NextSurface, which makes it easier to merge the two calls. Differential Revision: https://phabricator.services.mozilla.com/D50877
aa9475c27a6d5c4359f3a6d1c058ef9b1b440f5b: Bug 1594950 - Bake the layer size and its opaqueness into the layer, don't allow mutating it. r=jrmuizel
Markus Stange <mstange@themasta.com> - Wed, 13 Nov 2019 18:46:02 +0000 - rev 501813
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1594950 - Bake the layer size and its opaqueness into the layer, don't allow mutating it. r=jrmuizel These settings are now supplied during layer creation and never change. Consumers must now create new NativeLayer objects if they want to change size or toggle opaqueness. This aligns the NativeLayer API with DirectComposition's capabilities. It also simplifies swap chain management. Differential Revision: https://phabricator.services.mozilla.com/D51757
d791bfa31f08ec478b2ef6ca4f89b3a8849d723b: bug 1412438 - add preference to disable HPKP by default r=jcj
Dana Keeler <dkeeler@mozilla.com> - Wed, 13 Nov 2019 18:35:35 +0000 - rev 501812
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
bug 1412438 - add preference to disable HPKP by default r=jcj As Chrome has removed support for the HPKP (HTTP Public Key Pinning) header, continuing to support it in Firefox is a compatibility risk. This patch adds the preference "security.cert_pinning.hpkp.enabled" and sets it to false by default. As such, the platform will no longer process the HPKP header nor consult any cached HPKP information for certificate pins. Preloaded (statically-compiled) pins are still enabled in Firefox by default. This patch also disables dynamically setting pins via our remote security settings infrastructure, as it uses the same backend and represents similar compatibility risk. Differential Revision: https://phabricator.services.mozilla.com/D52773
c17276cc50c4d18a28a8653028f9489ba998d9bc: Bug 1595212 - Use MaybeUninit in nsString tests. r=SimonSapin
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 13 Nov 2019 12:39:23 +0000 - rev 501811
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1595212 - Use MaybeUninit in nsString tests. r=SimonSapin Differential Revision: https://phabricator.services.mozilla.com/D52824
da8d5a96f3c8f93be0a4ca787eedd410dcf3b0c8: Bug 1595285 - Fix TestUtils.waitForCondition to not use setInterval. r=mak
Emilio Cobos Álvarez <emilio@crisal.io> - Wed, 13 Nov 2019 18:24:02 +0000 - rev 501810
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1595285 - Fix TestUtils.waitForCondition to not use setInterval. r=mak The test that is timing out with these patches does something relatively simple: await TestUtils.waitForCondition(async function() { let color = await ContentTask.spawn(browserWindow, async function() { /* Do stuff... */ }); return color == something; }); await closeWindow(browserWindow); Turns out that this can intermittently leak the window due to waitForCondition using setInterval. setInterval can schedule multiple tasks while awaiting for the inner ContentTask. What this means, is that we may still have a ContentTask awaiting us when we get to close the window. Closing the window makes the ContentTask not finish, and thus we leak a promise keeping alive the window in gPromises: https://searchfox.org/mozilla-central/rev/6566d92dd46417a2f57e75c515135ebe84c9cef5/testing/mochitest/BrowserTestUtils/ContentTask.jsm#24 Which means that we keep alive the window all the way until shutdown. Fix it by ensuring that we only run one task at a time. Differential Revision: https://phabricator.services.mozilla.com/D52833
2284a535c8bc5a34c448665c99bdf0d7ea2d73f2: Bug 1588142 - Prevent internal pages from flashing the URL on reload r=Gijs
Kirk Steuber <ksteuber@mozilla.com> - Tue, 12 Nov 2019 18:01:01 +0000 - rev 501809
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1588142 - Prevent internal pages from flashing the URL on reload r=Gijs Converting about:preferences's root from a xul:window to an html:html involves moving the Fluent-translated title attribute to a title tag, which starts empty and is populated by Fluent. The initially-empty title tag causes the title bar to flash "about:preferences" on reload. This patch ignores empty title updates via DOMTitleChanged events to prevent this. This is only done for internal pages (i.e. pages with a system principal). Differential Revision: https://phabricator.services.mozilla.com/D52289
939b6b3922c2802abedb336712b08e605687e716: Bug 1588142 - Test fixes r=Gijs
Kirk Steuber <ksteuber@mozilla.com> - Tue, 12 Nov 2019 18:00:28 +0000 - rev 501808
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1588142 - Test fixes r=Gijs Differential Revision: https://phabricator.services.mozilla.com/D51714
1a5f2b044f827e6063218f6f6ff6a6b7e6066106: Bug 1588142 - Move Fluent about:preferences title attribute to a title tag r=fluent-reviewers,Gijs
Kirk Steuber <ksteuber@mozilla.com> - Tue, 12 Nov 2019 18:00:05 +0000 - rev 501807
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1588142 - Move Fluent about:preferences title attribute to a title tag r=fluent-reviewers,Gijs Differential Revision: https://phabricator.services.mozilla.com/D51713
87336cc7f8a1afe7dbd042fd23de5ae3010b0845: Bug 1588142 - about:preferences - migrate the root xul:window element to an html:html element r=Gijs,bgrins
Kirk Steuber <ksteuber@mozilla.com> - Wed, 13 Nov 2019 17:46:30 +0000 - rev 501806
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1588142 - about:preferences - migrate the root xul:window element to an html:html element r=Gijs,bgrins Differential Revision: https://phabricator.services.mozilla.com/D51712
da9476881d622b2d519f589f39d586f974ddb1e1: Bug 1595762: Make type object loads subject to CSP frame ancestors. r=jkt,annevk
Christoph Kerschbaumer <ckerschb@christophkerschbaumer.com> - Wed, 13 Nov 2019 14:52:55 +0000 - rev 501805
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1595762: Make type object loads subject to CSP frame ancestors. r=jkt,annevk Differential Revision: https://phabricator.services.mozilla.com/D52806
e7a759d68461596d4988c54e8c8e23b9a853e6ae: Bug 1595145 - Allow `GeckoInputStream#read()` to timeout. r=geckoview-reviewers,agi,esawin
James Willcox <snorp@snorp.net> - Wed, 13 Nov 2019 15:38:51 +0000 - rev 501804
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1595145 - Allow `GeckoInputStream#read()` to timeout. r=geckoview-reviewers,agi,esawin Differential Revision: https://phabricator.services.mozilla.com/D52382
9a4d7144206139470df276d6d0a26a99068aa0ab: Bug 1595144 - Throw IOException when trying to read a closed GeckoInputStream r=geckoview-reviewers,agi
James Willcox <snorp@snorp.net> - Wed, 13 Nov 2019 15:38:38 +0000 - rev 501803
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1595144 - Throw IOException when trying to read a closed GeckoInputStream r=geckoview-reviewers,agi Differential Revision: https://phabricator.services.mozilla.com/D52381
e2b8a34e2aac27d21773cb2d3da1278f47550e4f: Bug 1582741 - Add values to the native allocation payload; r=gerald
Greg Tatum <gtatum@mozilla.com> - Wed, 13 Nov 2019 16:19:16 +0000 - rev 501802
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1582741 - Add values to the native allocation payload; r=gerald This commit adds the memory address of the allocation and the thread id of the allocation to the payload. These both are required for properly processing the balanced allocations on the front-end. All of the native allocation payloads are now stored on the main thread, and so are disassociated from the thread where they were generated. Differential Revision: https://phabricator.services.mozilla.com/D51938
439f620efb11ff3e421a3ffdab1deb6b76b79281: Bug 1592625 - All threads' allocation markers get stored on the main thread; r=gerald
Greg Tatum <gtatum@mozilla.com> - Wed, 13 Nov 2019 16:19:11 +0000 - rev 501801
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1592625 - All threads' allocation markers get stored on the main thread; r=gerald This change makes it so that all allocations (from any thread in a process) are stored on the main thread in the profile. This way it's easy to balance allocations with frees. Memory happens more in a per-process model, than a per-thread model. The front-end can then process the information and display it in more interesting ways. Before allocations and deallocations were only stored on the thread where they were being generated. It was easy to miss deallocations with the old model. Differential Revision: https://phabricator.services.mozilla.com/D51937
5991133b6ac7b2535495c4f0a1ea3011f08885d1: Bug 1582741 - Create a test for balanced native allocation; r=canaltinova
Greg Tatum <gtatum@mozilla.com> - Wed, 13 Nov 2019 16:19:07 +0000 - rev 501800
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1582741 - Create a test for balanced native allocation; r=canaltinova This file adds coverage for the balanced native allocations feature from the previous commit. It asserts that a de-allocation will have a matching allocation. Differential Revision: https://phabricator.services.mozilla.com/D51936
b37cf462c34198a34ffe38ec1b9fc0ca56ab9a25: Bug 1582741 - Balance the frees to the allocations in native allocation tracking; r=njn,gerald
Greg Tatum <gtatum@mozilla.com> - Wed, 13 Nov 2019 16:17:38 +0000 - rev 501799
Push 36801 by dvarga@mozilla.com at Thu, 14 Nov 2019 17:12:31 +0000
Bug 1582741 - Balance the frees to the allocations in native allocation tracking; r=njn,gerald This patch creates a HashSet that tracks the allocations that are tracked by the profiler. This way, we only collect markers for deallocations that have a matching allocation. A following commit makes it so that all of the markers are collected on the main thread, but for now this is still done on a per-thread basis. Differential Revision: https://phabricator.services.mozilla.com/D51935
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip