searching for reviewer(billm)
34cf0986960016de09041a9c8b62a0f8173ffd83: Bug 1207696 Part 1e - Disable crash reporting when recording/replaying, r=billm.
Brian Hackett <bhackett1024@gmail.com> - Mon, 23 Jul 2018 14:33:42 +0000 - rev 821755
Push 117191 by maglione.k@gmail.com at Tue, 24 Jul 2018 02:14:48 +0000
Bug 1207696 Part 1e - Disable crash reporting when recording/replaying, r=billm.
92fc9eca3135c077362eec871fb0015b1440f552: Bug 1207696 Part 10g - Initialize replay-specific and middleman state, r=billm.
Brian Hackett <bhackett1024@gmail.com> - Sun, 22 Jul 2018 11:40:24 +0000 - rev 821371
Push 117078 by bmo:gl@mozilla.com at Mon, 23 Jul 2018 05:29:28 +0000
Bug 1207696 Part 10g - Initialize replay-specific and middleman state, r=billm.
6d66e812954ebcd3cbeae69fce173d2d93915273: Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 21 Dec 2017 20:38:37 +0100 - rev 761570
Push 100977 by bmo:jyavenard@mozilla.com at Thu, 01 Mar 2018 08:39:50 +0000
Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm MozReview-Commit-ID: myKnMDZclC
73e31f4d386f503fa297515d35adac98949c0a30: Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 21 Dec 2017 20:38:37 +0100 - rev 758945
Push 100234 by bmo:jyavenard@mozilla.com at Fri, 23 Feb 2018 13:20:57 +0000
Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm MozReview-Commit-ID: myKnMDZclC
1d12b20b69635e32d14346a556f3ace1b482f7dc: Bug 1348361: Make launching of subprocesses async. r=billm draft
Stephen A Pohl <spohl.mozilla.bugs@gmail.com> - Fri, 16 Feb 2018 10:24:21 -0500 - rev 757556
Push 99774 by bmo:agaynor@mozilla.com at Tue, 20 Feb 2018 20:22:23 +0000
Bug 1348361: Make launching of subprocesses async. r=billm MozReview-Commit-ID: I6i44kdl9dU
a0709ef63ccae04707ebb95aaa1c10c68c1dffae: Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 21 Dec 2017 20:38:37 +0100 - rev 754076
Push 98748 by bmo:jyavenard@mozilla.com at Mon, 12 Feb 2018 20:33:03 +0000
Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm MozReview-Commit-ID: myKnMDZclC
ed1ad83b23f24057524770fd7e145ea5f19bdeda: Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 21 Dec 2017 20:38:37 +0100 - rev 749964
Push 97529 by bmo:jyavenard@mozilla.com at Thu, 01 Feb 2018 10:07:26 +0000
Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm MozReview-Commit-ID: myKnMDZclC
6023858e3637ff2de718e5ae87544f73ccb9141b: Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 21 Dec 2017 20:38:37 +0100 - rev 749935
Push 97527 by bmo:jyavenard@mozilla.com at Thu, 01 Feb 2018 08:54:42 +0000
Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm MozReview-Commit-ID: myKnMDZclC
03c14ea47865f40b1da9a30191d9948ee07e49aa: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 749262
Push 97359 by bmo:gl@mozilla.com at Wed, 31 Jan 2018 05:06:52 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v (grafted from 308a4ed50826254e195fa2f4a14334d4114bd1f9)
308a4ed50826254e195fa2f4a14334d4114bd1f9: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm draft
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 749191
Push 97349 by bbirtles@mozilla.com at Wed, 31 Jan 2018 02:59:16 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v
209807e768dd462c5c8a00006cc7129ecd1e0705: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm draft
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 748971
Push 97286 by bbirtles@mozilla.com at Tue, 30 Jan 2018 19:06:18 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v
8a052f9c925ceb5cab200655d5c1c3d0469e4c8c: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm draft
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 727778
Push 96773 by bmo:bbirtles@mozilla.com at Thu, 25 Jan 2018 05:42:33 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v
a09421e3d50a0340af7b8db2057c1c53fe2bc75d: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm draft
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 727759
Push 96772 by bmo:bbirtles@mozilla.com at Thu, 25 Jan 2018 05:40:41 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v
085638d6b1e58dca1ca3690359c21ea334e82fc4: Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 21 Dec 2017 20:38:37 +0100 - rev 723522
Push 96452 by bmo:jyavenard@mozilla.com at Tue, 23 Jan 2018 13:24:17 +0000
Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm MozReview-Commit-ID: myKnMDZclC
bcca54b66b0963c8daa2124203d99be2ecddb0c9: Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm draft
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 21 Dec 2017 20:38:37 +0100 - rev 721804
Push 95953 by bmo:jyavenard@mozilla.com at Wed, 17 Jan 2018 21:46:35 +0000
Bug 1426067 - P4. Prevent any data race on monitor as the object gets deleted. r?billm MozReview-Commit-ID: myKnMDZclC
4efc37f978d2817177068b0df224fcdc3abebeee: Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm
cku <cku@mozilla.com> - Wed, 20 Dec 2017 11:46:13 +0800 - rev 721525
Push 95856 by jwatt@jwatt.org at Wed, 17 Jan 2018 10:55:16 +0000
Bug 1207734 - Part 6. Fix an assertion from the early pref access checking. r=billm MozReview-Commit-ID: 8GgVojlNy3v
a30d2216e0b9c8fc902f5e1704eafabab828fcff: Bug 1373708 - Part 2: Wait until all tabs are closed. r=billm
Liang-Heng Chen <xeonchen@gmail.com> - Thu, 07 Sep 2017 18:16:00 -0400 - rev 718704
Push 95038 by maglione.k@gmail.com at Wed, 10 Jan 2018 20:53:05 +0000
Bug 1373708 - Part 2: Wait until all tabs are closed. r=billm MozReview-Commit-ID: 2Ky8t2jpDyY
2cfdaedf635996efdc462bb12d5075b84b3e93e8: Bug 1397426 - Ensure we attempt to activate docShell of current tab after reacting to sidemode or occlusionstate change events. r=billm
Mike Conley <mconley@mozilla.com> - Thu, 21 Dec 2017 13:40:52 -0500 - rev 716798
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Ensure we attempt to activate docShell of current tab after reacting to sidemode or occlusionstate change events. r=billm During the macOS fullscreen mode change, the window entering fullscreen reports being occluded for a brief time (presumably due to the "stretch" effect that macOS is applying overtop of the window). This causes us to preserve the layers for the selected tab, and deactivate its docShell. According to https://bugzilla.mozilla.org/show_bug.cgi?id=1279086#c34, we preserve layers like this when minimizing or fully occluding the window. This way, we avoid a flicker when the window is un-minimized or partially revealed. However, if during that transition, the mouse hovers over a background tab (which is the case during the automated tests) and an async tab switcher doesn't already exist, we can trigger a warming attempt on that background tab, which creates an async tab switcher, and causes the switcher to run its init() method. Beyond setting some initial state, the init() method also makes it so that the initial browser at the time of calling init() sets preserve layers to false. If we get into this situation, then what we end up with is a tab that is rendering layers, is no longer preserving them, but the docShell is not activated. Soon after, the async tab switcher responds to the occlusionstatechange event when the window is revealed again. Before this patch, we did nothing, since it was assumed that postActions would eventually activate the docShell. However, since warming isn't currently activated by default, the async tab switcher soon destroys itself, and the initial tab's docShell is never activated. This causes the browser_domFullscreen_fullscreenMode.js test to hang (and probably other bugs as well). This patch makes it so that if we see an occlusionstatechange or sizemodechange event when the async tab switcher exists, and the window is no longer minimized or fully occluded, that we attempt to activate the currently selected tab's docShell. MozReview-Commit-ID: yJTUj8bBrs
c592bf74cad182c919e808892c1ee3859fb38d53: Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 19 Dec 2017 08:44:18 -0800 - rev 716797
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm MozReview-Commit-ID: IIMmwrgJUV6
8605e2ebcc92df713072d4923ecc21c5a62fa827: Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 21 Nov 2017 16:52:48 -0500 - rev 716796
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm Calling GetPresShell() might create a content viewer, which might cause script to run. This is bad if there's a ForcePaint message queued up, because it could mean running the force painting code while we're still in the midst of making a tab hidden, which would put us in an inconsistent state. MozReview-Commit-ID: 3rw2wGllGdk
707a2b0aede11d52aa5ab818a975170f894ba550: Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 20 Nov 2017 11:41:11 -0500 - rev 716795
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm This assumption also mirrors how non-remote browsers have their docShells active by default. In order to do this, I also have to increase the initial epoch's for the TabParent and TabChild, as if a RenderLayers has been called. Originally, since the epochs initted at 0, and the epochs stored by the [Layer|WebRender]TransactionParent were also initted at 0, we'd hit this branch: https://searchfox.org/mozilla-central/rev/c633ffa4c4611f202ca11270dcddb7b29edddff8/gfx/layers/ipc/LayerTransactionParent.cpp#703 and then we'd never alert the TabParent about the layer upload. MozReview-Commit-ID: 6PP1eCnisYK
3fa35817d29d5fe75e59f92cb794dcd6adb4f9b4: Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 17 Nov 2017 09:55:29 -0800 - rev 716794
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm This is necessary because sometimes the async tab switcher will instantiate when there already exists some background tabs that are rendering via print preview. When that happens, it's important for the state to be set correctly for them so that we don't accidentally treat them as still loading, and wait (forever) for them to report having finished loading. MozReview-Commit-ID: 2dwo5WlXlgJ
f6e07e9760454bdb813ab63b1c5b15d4d6ff259f: Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 23 Oct 2017 17:01:48 -0400 - rev 716793
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm Tab warming was originally disabled in this test because it was accidentally setting the DocShell to be active at an unexpected time. Because tab warming no longer activates DocShells, we can revert this change, though we also have to make it deal with the fact that switching tabs no longer makes docShells become activate immediately. MozReview-Commit-ID: K0fiA5AVfEm
d39683d8f79f01c24b34625988e0ba39535bf587: Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm
Mike Conley <mconley@mozilla.com> - Mon, 25 Sep 2017 13:55:48 -0400 - rev 716792
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm MozReview-Commit-ID: KWwDee0ujR
44d6efb9fa693766d667adb95281edbc9954d16d: Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:35 -0400 - rev 716791
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm MozReview-Commit-ID: Go2EdMXGwa7
f77d887fffcb7cef5ddb5c224639496cc77aac75: Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 11:27:29 -0400 - rev 716790
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm MozReview-Commit-ID: 1bBNwew7uCk
4dd5d1624aba5390d015023c9d836f12bf5f3d16: Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm
Mike Conley <mconley@mozilla.com> - Tue, 07 Nov 2017 15:08:47 -0500 - rev 716789
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm MozReview-Commit-ID: 7UT036vUY85
7dc566272fee7b5bb2e16ed0e3277915fb792e59: Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm
Mike Conley <mconley@mozilla.com> - Wed, 22 Nov 2017 10:21:34 -0800 - rev 716788
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm MozReview-Commit-ID: KTDhXM7PRdc
b0c38584a789814fc80bfd3c139e23d7ab193417: Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:05 -0400 - rev 716787
Push 94501 by bmo:ystartsev@mozilla.com at Sat, 06 Jan 2018 10:41:25 +0000
Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm Originally, setting the active state on the DocShell for remote browsers also did the work of making the TabChild render its layers and upload them to the compositor. This patch adds a new renderLayers method to nsITabParent which allows more fine-grained control - we can now, for example, cause layers to be rendered and uploaded without activating the DocShell. Note that if one activates or deactivates the DocShell, we'll still do the work of attempting to render / clear the layers if it hasn't already been done. MozReview-Commit-ID: KkLaMDTzfHi
76f2d740838d2666c2de66f3f0687a66b28f9dab: Bug 1397426 - Ensure we attempt to activate docShell of current tab after reacting to sidemode or occlusionstate change events. r?billm draft
Mike Conley <mconley@mozilla.com> - Thu, 21 Dec 2017 13:40:52 -0500 - rev 715466
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Ensure we attempt to activate docShell of current tab after reacting to sidemode or occlusionstate change events. r?billm During the macOS fullscreen mode change, the window entering fullscreen reports being occluded for a brief time (presumably due to the "stretch" effect that macOS is applying overtop of the window). This causes us to preserve the layers for the selected tab, and deactivate its docShell. According to https://bugzilla.mozilla.org/show_bug.cgi?id=1279086#c34, we preserve layers like this when minimizing or fully occluding the window. This way, we avoid a flicker when the window is un-minimized or partially revealed. However, if during that transition, the mouse hovers over a background tab (which is the case during the automated tests) and an async tab switcher doesn't already exist, we can trigger a warming attempt on that background tab, which creates an async tab switcher, and causes the switcher to run its init() method. Beyond setting some initial state, the init() method also makes it so that the initial browser at the time of calling init() sets preserve layers to false. If we get into this situation, then what we end up with is a tab that is rendering layers, is no longer preserving them, but the docShell is not activated. Soon after, the async tab switcher responds to the occlusionstatechange event when the window is revealed again. Before this patch, we did nothing, since it was assumed that postActions would eventually activate the docShell. However, since warming isn't currently activated by default, the async tab switcher soon destroys itself, and the initial tab's docShell is never activated. This causes the browser_domFullscreen_fullscreenMode.js test to hang (and probably other bugs as well). This patch makes it so that if we see an occlusionstatechange or sizemodechange event when the async tab switcher exists, and the window is no longer minimized or fully occluded, that we attempt to activate the currently selected tab's docShell. MozReview-Commit-ID: yJTUj8bBrs
f1faa794791a9c620a1cd7a28c67029134d63933: Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm draft
Mike Conley <mconley@mozilla.com> - Tue, 19 Dec 2017 08:44:18 -0800 - rev 715465
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm MozReview-Commit-ID: IIMmwrgJUV6
1c4b1ad28467fc6960eaa7cb744e47dd191b30f5: Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm draft
Mike Conley <mconley@mozilla.com> - Tue, 21 Nov 2017 16:52:48 -0500 - rev 715464
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm Calling GetPresShell() might create a content viewer, which might cause script to run. This is bad if there's a ForcePaint message queued up, because it could mean running the force painting code while we're still in the midst of making a tab hidden, which would put us in an inconsistent state. MozReview-Commit-ID: 3rw2wGllGdk
4ca9f692635e3a3a1ec8e626d0db24f2e512ec9a: Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm draft
Mike Conley <mconley@mozilla.com> - Mon, 20 Nov 2017 11:41:11 -0500 - rev 715463
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm This assumption also mirrors how non-remote browsers have their docShells active by default. In order to do this, I also have to increase the initial epoch's for the TabParent and TabChild, as if a RenderLayers has been called. Originally, since the epochs initted at 0, and the epochs stored by the [Layer|WebRender]TransactionParent were also initted at 0, we'd hit this branch: https://searchfox.org/mozilla-central/rev/c633ffa4c4611f202ca11270dcddb7b29edddff8/gfx/layers/ipc/LayerTransactionParent.cpp#703 and then we'd never alert the TabParent about the layer upload. MozReview-Commit-ID: 6PP1eCnisYK
4b1e2fb945f1dc4591c56f836a1caa9adeea9eb4: Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm draft
Mike Conley <mconley@mozilla.com> - Fri, 17 Nov 2017 09:55:29 -0800 - rev 715462
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm This is necessary because sometimes the async tab switcher will instantiate when there already exists some background tabs that are rendering via print preview. When that happens, it's important for the state to be set correctly for them so that we don't accidentally treat them as still loading, and wait (forever) for them to report having finished loading. MozReview-Commit-ID: 2dwo5WlXlgJ
874f112e4368a037b4baf02f205198c0f598b5b8: Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm draft
Mike Conley <mconley@mozilla.com> - Mon, 23 Oct 2017 17:01:48 -0400 - rev 715461
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm Tab warming was originally disabled in this test because it was accidentally setting the DocShell to be active at an unexpected time. Because tab warming no longer activates DocShells, we can revert this change, though we also have to make it deal with the fact that switching tabs no longer makes docShells become activate immediately. MozReview-Commit-ID: K0fiA5AVfEm
1840908f74a1ccb9aa50ce95d57cf38d5e55efa0: Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm draft
Mike Conley <mconley@mozilla.com> - Mon, 25 Sep 2017 13:55:48 -0400 - rev 715460
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm MozReview-Commit-ID: KWwDee0ujR
f12e8c368807028f88456c1649a46235cd7e8d97: Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm draft
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:35 -0400 - rev 715459
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm MozReview-Commit-ID: Go2EdMXGwa7
0e59b548c6c01d7feaf9f40c282ab2f55e47bab7: Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm draft
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 11:27:29 -0400 - rev 715458
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm MozReview-Commit-ID: 1bBNwew7uCk
873b6b91973b248c5b11ae8a136811a163f94e81: Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm draft
Mike Conley <mconley@mozilla.com> - Tue, 07 Nov 2017 15:08:47 -0500 - rev 715457
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - When short-circuiting a TabParent::RenderLayers call, still fire the layer tree event if we've been preserving layers. r=billm MozReview-Commit-ID: 7UT036vUY85
3909bfac189a980784fff998c6a71b1b38e7c9aa: Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm draft
Mike Conley <mconley@mozilla.com> - Wed, 22 Nov 2017 10:21:34 -0800 - rev 715456
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Rename mRenderingLayers to mRenderLayers. r=billm MozReview-Commit-ID: KTDhXM7PRdc
6c53729ae4b07c67d9e3de99c12e1165a85ffaac: Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm draft
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:05 -0400 - rev 715455
Push 94165 by mconley@mozilla.com at Wed, 03 Jan 2018 23:25:52 +0000
Bug 1397426 - Add IPC interface to tell TabChild's to render and clear layers, distinct from setting the active state on the DocShell. r=billm Originally, setting the active state on the DocShell for remote browsers also did the work of making the TabChild render its layers and upload them to the compositor. This patch adds a new renderLayers method to nsITabParent which allows more fine-grained control - we can now, for example, cause layers to be rendered and uploaded without activating the DocShell. Note that if one activates or deactivates the DocShell, we'll still do the work of attempting to render / clear the layers if it hasn't already been done. MozReview-Commit-ID: KkLaMDTzfHi
81b913e0975e53396a08cf4c8c7d2cae27a201df: Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm draft
Mike Conley <mconley@mozilla.com> - Tue, 19 Dec 2017 08:44:18 -0800 - rev 713208
Push 93573 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 20:21:44 +0000
Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm MozReview-Commit-ID: IIMmwrgJUV6
49ea45c0f42ebd4a8c47bd5b1d2d8f7c67f0312b: Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm draft
Mike Conley <mconley@mozilla.com> - Tue, 19 Dec 2017 08:44:18 -0800 - rev 713200
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - Expose renderLayers state via nsITabParent and lazily retrieve initial tab states in async tab switcher. r=billm MozReview-Commit-ID: IIMmwrgJUV6
ee0ec36cb5f1a8e1404b6c9161eac5f0df23fccd: Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm draft
Mike Conley <mconley@mozilla.com> - Tue, 21 Nov 2017 16:52:48 -0500 - rev 713199
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - TabChild::MakeHidden shouldn't cause script to run. r=billm Calling GetPresShell() might create a content viewer, which might cause script to run. This is bad if there's a ForcePaint message queued up, because it could mean running the force painting code while we're still in the midst of making a tab hidden, which would put us in an inconsistent state. MozReview-Commit-ID: 3rw2wGllGdk
6ee1dfb185a81d327b26bf5d05823377969c0f79: Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm draft
Mike Conley <mconley@mozilla.com> - Mon, 20 Nov 2017 11:41:11 -0500 - rev 713198
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - Make TabParent's assume they're rendering layers by default on construction. r=billm This assumption also mirrors how non-remote browsers have their docShells active by default. In order to do this, I also have to increase the initial epoch's for the TabParent and TabChild, as if a RenderLayers has been called. Originally, since the epochs initted at 0, and the epochs stored by the [Layer|WebRender]TransactionParent were also initted at 0, we'd hit this branch: https://searchfox.org/mozilla-central/rev/c633ffa4c4611f202ca11270dcddb7b29edddff8/gfx/layers/ipc/LayerTransactionParent.cpp#703 and then we'd never alert the TabParent about the layer upload. MozReview-Commit-ID: 6PP1eCnisYK
c6710a45aa3f567b70e2824f8ebedfd4e3c76d3c: Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm draft
Mike Conley <mconley@mozilla.com> - Fri, 17 Nov 2017 09:55:29 -0800 - rev 713197
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - Add hasLayers to nsITabParent and use it in the async tab switcher. r=billm This is necessary because sometimes the async tab switcher will instantiate when there already exists some background tabs that are rendering via print preview. When that happens, it's important for the state to be set correctly for them so that we don't accidentally treat them as still loading, and wait (forever) for them to report having finished loading. MozReview-Commit-ID: 2dwo5WlXlgJ
e2ddb6c3fc71e561bdeac42e0c207c8067a41113: Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm draft
Mike Conley <mconley@mozilla.com> - Mon, 23 Oct 2017 17:01:48 -0400 - rev 713196
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - Stop disabling tab warming in browser_bug343515.js. r=billm Tab warming was originally disabled in this test because it was accidentally setting the DocShell to be active at an unexpected time. Because tab warming no longer activates DocShells, we can revert this change, though we also have to make it deal with the fact that switching tabs no longer makes docShells become activate immediately. MozReview-Commit-ID: K0fiA5AVfEm
6f0d8a23aaac97a24b1974d8ba27b5254a04e371: Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm draft
Mike Conley <mconley@mozilla.com> - Mon, 25 Sep 2017 13:55:48 -0400 - rev 713195
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - Fix block comment formatting in nsITabParent.idl. r=billm MozReview-Commit-ID: KWwDee0ujR
01b3063814abb8b67467c9b4db0ed4ec128ea1fb: Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm draft
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 10:27:35 -0400 - rev 713194
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - Make async tab switcher use new nsITabParent renderLayers function. r=billm MozReview-Commit-ID: Go2EdMXGwa7
3babf91a131d5b210a47648dde1b9237565f4620: Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm draft
Mike Conley <mconley@mozilla.com> - Fri, 03 Nov 2017 11:27:29 -0400 - rev 713193
Push 93565 by bmo:mconley@mozilla.com at Tue, 19 Dec 2017 19:16:44 +0000
Bug 1397426 - Rename TabChild's notion of "active tabs" to "visible tabs" and move logic into renderLayers. r=billm MozReview-Commit-ID: 1bBNwew7uCk