searching for reviewer(kats)
5907e3987aff477b899ac7a327a13c1cf848971d: Bug 1563717 - Divide the RCD-RSF ScrollFrame item's clip rect by the resolution. r=kats
Botond Ballo <botond@mozilla.com> - Sat, 27 Jul 2019 02:31:37 +0000 - rev 484989
Push 113786 by dvarga@mozilla.com at Sat, 27 Jul 2019 09:34:13 +0000
Bug 1563717 - Divide the RCD-RSF ScrollFrame item's clip rect by the resolution. r=kats The clip rect is derived from the composition bounds, which is in units that are outside the resolution, but it's applied to the ScrollFrame item which is inside the resolution. Differential Revision: https://phabricator.services.mozilla.com/D37939
0c25260c4edf97fdfef11320c2a91bc0698b4c11: Bug 1547351 - Automatically set content process render root r=kats
Alexis Beingessner <a.beingessner@gmail.com> - Wed, 24 Jul 2019 14:10:56 +0000 - rev 484516
Push 113775 by aciure@mozilla.com at Thu, 25 Jul 2019 06:34:07 +0000
Bug 1547351 - Automatically set content process render root r=kats This implements the idea of automatically setting a content proc's render root based on the render root enclosing the iframe that points to it. There was a bit of cleanup in here that was a bit tricky to extract from the core patch revolving around how we use the Api(...) helper. This was to avoid the situation where we use the Api(...) helper before our render root is initialized, when we don't actually have to. I.e., when we just want the root WebRenderAPI in all cases. An alternative to this approach could be to fully built out the WebRender transactions and just queue those up to be sent. However, transaction building has various side effects which are committed before the transaction is actually sent, so we would have to build out some scheme for deferring those as well. This seemed simpler. Patch primarily written by :dthayer Differential Revision: https://phabricator.services.mozilla.com/D37078
77ef8e8bc669c9ecab4d94505b11b3cb732446c5: Bug 1547351 - Automatically set content process render root r=kats
Alexis Beingessner <a.beingessner@gmail.com> - Mon, 15 Jul 2019 13:18:44 +0000 - rev 482770
Push 113692 by nerli@mozilla.com at Mon, 15 Jul 2019 21:50:20 +0000
Bug 1547351 - Automatically set content process render root r=kats This implements the idea of automatically setting a content proc's render root based on the render root enclosing the iframe that points to it. There was a bit of cleanup in here that was a bit tricky to extract from the core patch revolving around how we use the Api(...) helper. This was to avoid the situation where we use the Api(...) helper before our render root is initialized, when we don't actually have to. I.e., when we just want the root WebRenderAPI in all cases. An alternative to this approach could be to fully built out the WebRender transactions and just queue those up to be sent. However, transaction building has various side effects which are committed before the transaction is actually sent, so we would have to build out some scheme for deferring those as well. This seemed simpler. Patch primarily written by :dthayer Differential Revision: https://phabricator.services.mozilla.com/D37078
46c9b479034f2c6ee710d8d5a703de4a07e77557: Bug 1547351 - Automatically set content process render root r=kats
Alexis Beingessner <a.beingessner@gmail.com> - Fri, 12 Jul 2019 14:14:22 +0000 - rev 482614
Push 113677 by apavel@mozilla.com at Fri, 12 Jul 2019 21:57:56 +0000
Bug 1547351 - Automatically set content process render root r=kats This implements the idea of automatically setting a content proc's render root based on the render root enclosing the iframe that points to it. There was a bit of cleanup in here that was a bit tricky to extract from the core patch revolving around how we use the Api(...) helper. This was to avoid the situation where we use the Api(...) helper before our render root is initialized, when we don't actually have to. I.e., when we just want the root WebRenderAPI in all cases. An alternative to this approach could be to fully built out the WebRender transactions and just queue those up to be sent. However, transaction building has various side effects which are committed before the transaction is actually sent, so we would have to build out some scheme for deferring those as well. This seemed simpler. Patch primarily written by :dthayer Differential Revision: https://phabricator.services.mozilla.com/D37078
8c6816b9c74c7b1328dd693dd2a5e4f963258bc9: Bug 1565168 - Add a webrender try preset. r=kats
Nicolas Silva <nsilva@mozilla.com> - Thu, 11 Jul 2019 17:23:08 +0000 - rev 482546
Push 113677 by apavel@mozilla.com at Fri, 12 Jul 2019 21:57:56 +0000
Bug 1565168 - Add a webrender try preset. r=kats Differential Revision: https://phabricator.services.mozilla.com/D37688
af34904f00c78daa52ed7970f64bbdd152acd508: Bug 1547351 - Automatically set content process render root r=kats
Alexis Beingessner <a.beingessner@gmail.com> - Fri, 12 Jul 2019 05:14:05 +0000 - rev 482534
Push 113677 by apavel@mozilla.com at Fri, 12 Jul 2019 21:57:56 +0000
Bug 1547351 - Automatically set content process render root r=kats This implements the idea of automatically setting a content proc's render root based on the render root enclosing the iframe that points to it. There was a bit of cleanup in here that was a bit tricky to extract from the core patch revolving around how we use the Api(...) helper. This was to avoid the situation where we use the Api(...) helper before our render root is initialized, when we don't actually have to. I.e., when we just want the root WebRenderAPI in all cases. An alternative to this approach could be to fully built out the WebRender transactions and just queue those up to be sent. However, transaction building has various side effects which are committed before the transaction is actually sent, so we would have to build out some scheme for deferring those as well. This seemed simpler. Patch primarily written by :dthayer Differential Revision: https://phabricator.services.mozilla.com/D37078
b294575c279c9681d0a26b1592f47014262f1d03: Bug 1547351 - Automatically set content process render root r=kats
Alexis Beingessner <a.beingessner@gmail.com> - Fri, 12 Jul 2019 03:19:28 +0000 - rev 482521
Push 113674 by dvarga@mozilla.com at Fri, 12 Jul 2019 10:08:07 +0000
Bug 1547351 - Automatically set content process render root r=kats This implements the idea of automatically setting a content proc's render root based on the render root enclosing the iframe that points to it. There was a bit of cleanup in here that was a bit tricky to extract from the core patch revolving around how we use the Api(...) helper. This was to avoid the situation where we use the Api(...) helper before our render root is initialized, when we don't actually have to. I.e., when we just want the root WebRenderAPI in all cases. An alternative to this approach could be to fully built out the WebRender transactions and just queue those up to be sent. However, transaction building has various side effects which are committed before the transaction is actually sent, so we would have to build out some scheme for deferring those as well. This seemed simpler. Patch primarily written by :dthayer Differential Revision: https://phabricator.services.mozilla.com/D37078
3ffe1c1e0dc87eb19af951597af73e3a591e2412: Bug 1289211 - Rename InfallibleTArray to nsTArray in gfx/ipc/ r=kats
Barret Rennie <barret@brennie.ca> - Wed, 10 Jul 2019 03:29:05 +0000 - rev 482210
Push 113654 by aiakab@mozilla.com at Wed, 10 Jul 2019 22:00:37 +0000
Bug 1289211 - Rename InfallibleTArray to nsTArray in gfx/ipc/ r=kats Differential Revision: https://phabricator.services.mozilla.com/D36953
b8f19d6b876273bc08c8e82bf72282d923a97a7d: Bug 1564846 - Do better at managing secondary windows in TestRunnerActivity r=kats
James Willcox <snorp@snorp.net> - Wed, 10 Jul 2019 15:36:15 +0000 - rev 482178
Push 113654 by aiakab@mozilla.com at Wed, 10 Jul 2019 22:00:37 +0000
Bug 1564846 - Do better at managing secondary windows in TestRunnerActivity r=kats Differential Revision: https://phabricator.services.mozilla.com/D37570
40010303c474166637b65e5f91dce5b07cf5a9a9: Bug 1500465 - Measure touch scroll latency and connect to telemetry. r=kats
Christina Cheung <ccheung@mozilla.com> - Tue, 09 Jul 2019 20:55:15 +0000 - rev 482000
Push 113647 by aciure@mozilla.com at Wed, 10 Jul 2019 09:46:39 +0000
Bug 1500465 - Measure touch scroll latency and connect to telemetry. r=kats Differential Revision: https://phabricator.services.mozilla.com/D36246
516d28fb9aebe12994d4bf960865ca65370b1ef6: Bug 1561435 - Reposition comments in gfx/, r=kats
Victor Porof <vporof@mozilla.com> - Wed, 26 Jun 2019 16:02:07 +0200 - rev 481384
Push 113609 by apavel@mozilla.com at Fri, 05 Jul 2019 16:39:58 +0000
Bug 1561435 - Reposition comments in gfx/, r=kats # ignore-this-changeset Differential Revision: https://phabricator.services.mozilla.com/D36025
9554ac45236fa9a256249587b238ee2e6a414849: Bug 1528937 - Test that taps are transformed correctly for out-of-process iframes. r=kats
Henri Sivonen <hsivonen@hsivonen.fi> - Wed, 03 Jul 2019 18:05:39 +0000 - rev 481190
Push 113602 by opoprus@mozilla.com at Thu, 04 Jul 2019 03:40:43 +0000
Bug 1528937 - Test that taps are transformed correctly for out-of-process iframes. r=kats Differential Revision: https://phabricator.services.mozilla.com/D36743
1cdac03c50cd9e75a45153c691309f590306aa6c: Bug 1561859 - [Wayland] Expose active DRM on Wayland in about:support & telemetry, r=kats
Martin Stransky <stransky@redhat.com> - Tue, 02 Jul 2019 09:17:22 +0000 - rev 480944
Push 113585 by aciure@mozilla.com at Tue, 02 Jul 2019 21:57:44 +0000
Bug 1561859 - [Wayland] Expose active DRM on Wayland in about:support & telemetry, r=kats Differential Revision: https://phabricator.services.mozilla.com/D36248
6e378fbef555113f365ba7f7f79f9ab0e661004e: Bug 1561859 - [Wayland] Expose active DRM on Wayland in about:support & telemetry, r=kats
Martin Stransky <stransky@redhat.com> - Mon, 01 Jul 2019 13:44:14 +0000 - rev 480793
Push 113569 by rgurzau@mozilla.com at Mon, 01 Jul 2019 22:22:20 +0000
Bug 1561859 - [Wayland] Expose active DRM on Wayland in about:support & telemetry, r=kats Differential Revision: https://phabricator.services.mozilla.com/D36248
da65877c0fec3c21af44c542bada87ea8e8c6eea: Bug 1561858 - Use only transforms outside of the subtree when computing the subtree transform to root. r=kats
Matt Woodrow <mwoodrow@mozilla.com> - Sun, 30 Jun 2019 21:03:04 +0000 - rev 480742
Push 113567 by opoprus@mozilla.com at Mon, 01 Jul 2019 10:09:01 +0000
Bug 1561858 - Use only transforms outside of the subtree when computing the subtree transform to root. r=kats Differential Revision: https://phabricator.services.mozilla.com/D36304
76c526cf901b20b7383524e0c3d0bfa82855cd20: Bug 1561726 - Add a test to exercise dragging the viewport scrollbar. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 28 Jun 2019 20:23:36 +0000 - rev 480633
Push 113561 by ncsoregi@mozilla.com at Sat, 29 Jun 2019 10:06:30 +0000
Bug 1561726 - Add a test to exercise dragging the viewport scrollbar. r=kats Differential Revision: https://phabricator.services.mozilla.com/D34259
fdaf7d75ccc9f79ecf13af083a5764f57cdb6190: Bug 1561726 - Modify dragVerticalScrollbar() to support dragging the viewport scrollbar as well. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 28 Jun 2019 20:23:08 +0000 - rev 480632
Push 113561 by ncsoregi@mozilla.com at Sat, 29 Jun 2019 10:06:30 +0000
Bug 1561726 - Modify dragVerticalScrollbar() to support dragging the viewport scrollbar as well. r=kats Dragging the viewport scrollbar is accomplished by passing in a window rather than an element. Note that we can't just pass in the window's document.documentElement, because coordinatesRelativeToScreen() would not give the correct result for it. This is turn is because for a scrollable <div>, getBoundingClientRect() returns the scroll frame's outer rect, but for the <html> element, getBoundingClientRect() returns the root scroll frame's inner rect. Differential Revision: https://phabricator.services.mozilla.com/D34258
8776353e9c153cc21048d0760449aa0843a1f4fe: Bug 1556058 - Update test expectations for Android 7.0 reftests; r=kats
Geoff Brown <gbrown@mozilla.com> - Fri, 28 Jun 2019 17:30:48 +0000 - rev 480615
Push 113558 by shindli@mozilla.com at Fri, 28 Jun 2019 23:24:53 +0000
Bug 1556058 - Update test expectations for Android 7.0 reftests; r=kats These changes are needed for consistently green runs with the new emulator with "-gpu on". Most changes are simple removal of fuzzy-if(geckoview) but I also needed to add at least one new fuzzy-if. In this configuration we can run reftests in just 2 chunks (20 minutes each on opt/30 minutes on debug). Differential Revision: https://phabricator.services.mozilla.com/D36258
5a18f5c929ab13bde25f7fff8ae72f87e8fa379c: Bug 1549976 - Implement popover render root r=kats,Gijs
Doug Thayer <dothayer@mozilla.com> - Fri, 21 Jun 2019 19:15:11 +0100 - rev 480499
Push 113553 by gijskruitbosch@gmail.com at Fri, 28 Jun 2019 15:13:51 +0000
Bug 1549976 - Implement popover render root r=kats,Gijs If we decide to just go with an overlay that sits fully over the window (which I don't personally see a perf problem with right now, but correct me if you can think of one), then this should be all we need. Differential Revision: https://phabricator.services.mozilla.com//D33819
60c8d0cdd443bad2f5c840196ea3a99ba45c28c1: Bug 1560600 - Don't allow WebRender for AMD on non-nightly for non-Windows platforms. r=kats
Andrew Osmond <aosmond@mozilla.com> - Fri, 21 Jun 2019 17:59:38 -0700 - rev 479935
Push 113505 by aosmond@gmail.com at Mon, 24 Jun 2019 17:56:43 +0000
Bug 1560600 - Don't allow WebRender for AMD on non-nightly for non-Windows platforms. r=kats Differential Revision: https://phabricator.services.mozilla.com/D35569
8d7491cb1c12fc69980a277e97d7c0f78582da18: Bug 1559518 - Use LayoutDevicePixel for BrowserChild visible rect and composition size. r=kats
Ryan Hunt <rhunt@eqrion.net> - Wed, 19 Jun 2019 18:20:52 +0000 - rev 479602
Push 113474 by rmaries@mozilla.com at Thu, 20 Jun 2019 11:21:48 +0000
Bug 1559518 - Use LayoutDevicePixel for BrowserChild visible rect and composition size. r=kats App units of a remote browser element in the parent process are different from app units inside the remote content in the child process. We should apply the appropriate conversions by exposing the relevant data as LayoutDevicePixel. Differential Revision: https://phabricator.services.mozilla.com/D35334
b0f2fc39f250ce173929d1f399cbe4818db118d1: Bug 1559859 - Always release mWidget in UiCompositorControllerChild::Destroy() r=kats
sotaro <sotaro.ikeda.g@gmail.com> - Tue, 18 Jun 2019 09:49:02 +0000 - rev 479136
Push 113465 by cbrindusan@mozilla.com at Wed, 19 Jun 2019 03:59:07 +0000
Bug 1559859 - Always release mWidget in UiCompositorControllerChild::Destroy() r=kats Differential Revision: https://phabricator.services.mozilla.com/D35210
e249cd75138b075397f22731aa94aa1ee9c803d6: Bug 1548247 - Fully recurse frame tree from APZCCallbackHelper r=kats
Doug Thayer <dothayer@mozilla.com> - Tue, 18 Jun 2019 22:03:08 +0000 - rev 479135
Push 113465 by cbrindusan@mozilla.com at Wed, 19 Jun 2019 03:59:07 +0000
Bug 1548247 - Fully recurse frame tree from APZCCallbackHelper r=kats I wasn't able to produce a situation in which this change matters, so I'm not certain that it's necessary, but it seems to be the correct thing to do given the problem fixed in nsGfxScrollFrame.cpp. Differential Revision: https://phabricator.services.mozilla.com/D31864
bf1be740ee4ad47ef0d378c3222bf6c16eaf4a5c: Bug 1548247 - Use aGuid's RenderRoot in RecvStart/StopAutoscroll r=kats
Doug Thayer <dothayer@mozilla.com> - Tue, 18 Jun 2019 22:03:04 +0000 - rev 479134
Push 113465 by cbrindusan@mozilla.com at Wed, 19 Jun 2019 03:59:07 +0000
Bug 1548247 - Use aGuid's RenderRoot in RecvStart/StopAutoscroll r=kats The work for the antecedent patch led me to stumble on a problem where we were not correctly stopping autoscroll. This was also due to a renderroot mismatch, which this patch addresses. The call comes through nsBaseWidget no matter what, it seems, so using mWrRootId.mRenderRoot seems to be incorrect. I couldn't see a more elegant fix than this. Differential Revision: https://phabricator.services.mozilla.com/D31863
c86eb07fe740f960e42a4b429de0a4e8b3634da9: Bug 1548247 - Correct and limit scroll update renderroot usage r=kats
Doug Thayer <dothayer@mozilla.com> - Tue, 18 Jun 2019 22:02:57 +0000 - rev 479133
Push 113465 by cbrindusan@mozilla.com at Wed, 19 Jun 2019 03:59:07 +0000
Bug 1548247 - Correct and limit scroll update renderroot usage r=kats There's two things going on here. 1) nsGfxScrollFrame is getting the wrong renderroot, because it's not correctly recursing up the frame tree. 2) Hiding behind that problem is that if we do correctly assign the renderroot, we end up blocking on both render roots updating if we don't, say, have a horizontal scroll option, because that leaves us with a wr::RenderRoot::Default. 2.1) We then still end up blocking on the default renderroot because we initialize the selector with WebRenderBridgeParent's mRenderRoot. Differential Revision: https://phabricator.services.mozilla.com/D31858
e593e11eff08e99f021de466e68964ca136cd62f: Bug 1559518 - Revert composition size changes as they also affect top level remote browsers. r=kats
Ryan Hunt <rhunt@eqrion.net> - Mon, 17 Jun 2019 16:09:28 +0000 - rev 479095
Push 113462 by btara@mozilla.com at Tue, 18 Jun 2019 04:15:10 +0000
Bug 1559518 - Revert composition size changes as they also affect top level remote browsers. r=kats This change was suspect to not work under full page zoom, but I thought it would be okay as it would only affect OOP-iframes. That was not true. Differential Revision: https://phabricator.services.mozilla.com/D35190
5c58b59524413e9cabe781105e2c48c6d8a6e463: Bug 1559570 - Use a different style change to trigger AllReflowHints for now. r=kats
Emilio Cobos Álvarez <emilio@crisal.io> - Mon, 17 Jun 2019 01:48:24 +0000 - rev 479073
Push 113459 by malexandru@mozilla.com at Mon, 17 Jun 2019 10:07:02 +0000
Bug 1559570 - Use a different style change to trigger AllReflowHints for now. r=kats box-sizing changes seem a bit less likely to be optimized away in the near future... Differential Revision: https://phabricator.services.mozilla.com/D35161
76571050b8ff538534f487366d1e72d1c70226e9: Bug 1556763 - Enable wrench blend reftests on android devices. r=kats
Jamie Nicol <jnicol@mozilla.com> - Sat, 15 Jun 2019 11:56:33 +0000 - rev 479043
Push 113453 by shindli@mozilla.com at Sat, 15 Jun 2019 21:56:53 +0000
Bug 1556763 - Enable wrench blend reftests on android devices. r=kats These now work on actual devices now, but must remain disabled on the emulator until bug 1555002 is fixed. Differential Revision: https://phabricator.services.mozilla.com/D34619
b8628b1c358c6997f5d1685770b192b0fa7c36c3: Bug 1559259 - Have APZ set mLayersId on WidgetEvent when not using WebRender. r=kats
Ryan Hunt <rhunt@eqrion.net> - Fri, 14 Jun 2019 23:12:15 +0000 - rev 479002
Push 113448 by apavel@mozilla.com at Sat, 15 Jun 2019 10:07:35 +0000
Bug 1559259 - Have APZ set mLayersId on WidgetEvent when not using WebRender. r=kats Differential Revision: https://phabricator.services.mozilla.com/D34939
6a4db4efaef6a7afab729f82dc9c8d18bea8d271: Bug 1558770 - Remove non-functional test. r=kats
Jean-Yves Avenard <jyavenard@mozilla.com> - Thu, 13 Jun 2019 00:35:30 +0000 - rev 478594
Push 113428 by opoprus@mozilla.com at Thu, 13 Jun 2019 10:07:38 +0000
Bug 1558770 - Remove non-functional test. r=kats The test is supposed to test that changing the preference layers.acceleration.disabled doesn't cause a crash, but this pref is only read on startup well before the test has a chance to run and switch the pref. It's not doing anything. Differential Revision: https://phabricator.services.mozilla.com/D34781
94b369f38c536a4cc3b308311b1e88825e581ff5: Bug 1558482 - Restrict the composition size to the visibleRect for OOP-iframes. r=kats
Ryan Hunt <rhunt@eqrion.net> - Tue, 11 Jun 2019 07:57:52 -0500 - rev 478570
Push 113426 by rhunt@eqrion.net at Thu, 13 Jun 2019 04:59:22 +0000
Bug 1558482 - Restrict the composition size to the visibleRect for OOP-iframes. r=kats Even if we don't have a root displayport, the composition size is still used for displayport margins calculations. For extremely tall iframes, this will create a displayport that is way to big. We should instead report a composition size that is equivalent to the visible rect for OOP-iframes. Differential Revision: https://phabricator.services.mozilla.com/D34528
c024e5eced2c80ec38c0b595f9bd1e20a0645b6e: Bug 1558482 - Only initialize the root displayport for the cross process root content document. r=kats
Ryan Hunt <rhunt@eqrion.net> - Tue, 11 Jun 2019 07:57:23 -0500 - rev 478569
Push 113426 by rhunt@eqrion.net at Thu, 13 Jun 2019 04:59:22 +0000
Bug 1558482 - Only initialize the root displayport for the cross process root content document. r=kats The root displayport has some assumptions built into it about being positioned at the origin and sized to the composition bounds that seem like they only apply to the cross process root content document. This commit changes us to avoid taking this code path for OOP-iframes. Differential Revision: https://phabricator.services.mozilla.com/D34527
f09dc8e08fa1b2ebf198f8942f3130ce13e8b199: Bug 1558276 - Make layers.dump and layers.dump-host-layers synonyms. r=kats
Botond Ballo <botond@mozilla.com> - Mon, 10 Jun 2019 20:34:34 +0000 - rev 478177
Push 113407 by cbrindusan@mozilla.com at Tue, 11 Jun 2019 09:45:25 +0000
Bug 1558276 - Make layers.dump and layers.dump-host-layers synonyms. r=kats Now they both work in opt builds, and they both work with advanced layers. For consistency, layers.dump-client-layers is also modified to work in opt builds. Differential Revision: https://phabricator.services.mozilla.com/D34413
4a1c99839cecdc6c20b7405c59a91030595d07d6: Bug 1554790 - Use reftest-resolution where appropriate in APZ scrollbar rendering reftests. r=kats
Botond Ballo <botond@mozilla.com> - Mon, 10 Jun 2019 21:23:51 +0000 - rev 478176
Push 113407 by cbrindusan@mozilla.com at Tue, 11 Jun 2019 09:45:25 +0000
Bug 1554790 - Use reftest-resolution where appropriate in APZ scrollbar rendering reftests. r=kats With this change, the tests in question pass on desktop, except for scrollbar-zoom-resolution-2.html which is annotated as failing. Differential Revision: https://phabricator.services.mozilla.com/D32775
421c96010e6734faeb6ec0cbdb04e86c5f0fffb6: Bug 1554790 - Add a reftest-resolution attribute. r=kats,hiro
Botond Ballo <botond@mozilla.com> - Tue, 11 Jun 2019 02:22:02 +0000 - rev 478175
Push 113407 by cbrindusan@mozilla.com at Tue, 11 Jun 2019 09:45:25 +0000
Bug 1554790 - Add a reftest-resolution attribute. r=kats,hiro Differential Revision: https://phabricator.services.mozilla.com/D32774
b418fcf242aa04e06c7e580706a1f90d6a77ded2: Bug 1554790 - Include the pres shell resolution in the post-scale for advanced layers as well. r=kats
Botond Ballo <botond@mozilla.com> - Tue, 11 Jun 2019 02:22:02 +0000 - rev 478174
Push 113407 by cbrindusan@mozilla.com at Tue, 11 Jun 2019 09:45:25 +0000
Bug 1554790 - Include the pres shell resolution in the post-scale for advanced layers as well. r=kats Differential Revision: https://phabricator.services.mozilla.com/D34422
aa00d643b6e620c776b97fa78b5e367945db19f9: Bug 1553045 - Place the fallback scroll metadata onto the async zoom container layer if there is one. r=kats
Botond Ballo <botond@mozilla.com> - Sat, 08 Jun 2019 17:49:38 +0000 - rev 477979
Push 113389 by ncsoregi@mozilla.com at Sun, 09 Jun 2019 09:14:13 +0000
Bug 1553045 - Place the fallback scroll metadata onto the async zoom container layer if there is one. r=kats This preserves the APZ invariant that if there is an async zoom container, then the RCD-RSF scroll metadata is on the same layer or descendant layers. Differential Revision: https://phabricator.services.mozilla.com/D34255
83e6d4980c56ad867555af98dcebc67b3ac3e803: Bug 1553045 - Have APZ support the RCD-RSF scroll metadata being on the async zoom container layer. r=kats
Botond Ballo <botond@mozilla.com> - Sat, 08 Jun 2019 17:49:30 +0000 - rev 477978
Push 113389 by ncsoregi@mozilla.com at Sun, 09 Jun 2019 09:14:13 +0000
Bug 1553045 - Have APZ support the RCD-RSF scroll metadata being on the async zoom container layer. r=kats This mostly already works, e.g. AsyncCompositionManager will apply both parts of the transform independently, just a check in APZCTreeManager:: ComputeTransformForNode() needed to be adjusted. Differential Revision: https://phabricator.services.mozilla.com/D34253
6e62e4cad2b12cfd279a494af6ab588fdc71a3d6: Bug 1557424 - Re-clamp the scroll offset if the composition bounds changes. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 07 Jun 2019 22:17:04 +0000 - rev 477931
Push 113386 by nbeleuzu@mozilla.com at Sat, 08 Jun 2019 09:51:50 +0000
Bug 1557424 - Re-clamp the scroll offset if the composition bounds changes. r=kats This is similar to bug 1551582, but concerns a main-thread change to the composition bounds rather than the scrollable rect; either can result in the scroll range shrinking and therefore a need to re-clamp the scroll offset. Differential Revision: https://phabricator.services.mozilla.com/D34211
01f72d6cc13b754b8250cc87fd1051714ce9a02b: Bug 1554790 - Use reftest-resolution where appropriate in APZ scrollbar rendering reftests. r=kats
Botond Ballo <botond@mozilla.com> - Fri, 31 May 2019 18:26:04 +0000 - rev 477499
Push 113351 by shindli@mozilla.com at Thu, 06 Jun 2019 10:13:05 +0000
Bug 1554790 - Use reftest-resolution where appropriate in APZ scrollbar rendering reftests. r=kats With this change, the tests in question pass on desktop, except for scrollbar-zoom-resolution-2.html which is annotated as failing. Differential Revision: https://phabricator.services.mozilla.com/D32775
3a41c4ed8bf3c803a2e2ee922ab3813631685b79: Bug 1554790 - Add a reftest-resolution attribute. r=kats,hiro
Botond Ballo <botond@mozilla.com> - Wed, 05 Jun 2019 01:53:45 +0000 - rev 477498
Push 113351 by shindli@mozilla.com at Thu, 06 Jun 2019 10:13:05 +0000
Bug 1554790 - Add a reftest-resolution attribute. r=kats,hiro Differential Revision: https://phabricator.services.mozilla.com/D32774
1b8cb27c53469e84802ad89f331138a247e43ad1: Bug 1557183 - Fix typos. r=kats
Bruce Mitchener <bruce.mitchener@gmail.com> - Wed, 05 Jun 2019 16:50:05 +0700 - rev 477475
Push 113344 by kgupta@mozilla.com at Thu, 06 Jun 2019 00:31:41 +0000
Bug 1557183 - Fix typos. r=kats [wrupdater] From https://github.com/servo/webrender/pull/3665
611d4651e1517bc18c82fccfb623972caa3dc1ad: Bug 1435586 - Use static gfxPlatform methods directly instead of requiring initialization. r=kats
Andrew Osmond <aosmond@mozilla.com> - Wed, 05 Jun 2019 08:46:19 -0400 - rev 477435
Push 113334 by aosmond@gmail.com at Wed, 05 Jun 2019 16:40:40 +0000
Bug 1435586 - Use static gfxPlatform methods directly instead of requiring initialization. r=kats gfxPlatform::GetSourceSurfaceForSurface and CreateDrawTargetForSurface are both static methods that we sometimes use via the pattern gfxPlatform::GetPlatform()->... This is problematic because this forces gfxPlatform to be initialized in the process, and in the GPU process, we don't support this. It should be safe to call these methods without initializing gfxPlatform, so this patch removes the GetPlatform() call. GetSourceSurfaceForSurface may end up initializing gfxPlatform anyways, depending on whether or not a DrawTarget was given. This should not be a concern for the crashes observed in bug 1435586. Differential Revision: https://phabricator.services.mozilla.com/D33785
0342dc8a3781dbb73501802c83aa5cfdf4c548a2: Bug 1533802 - Sticky nesting for C++, Rust, JS r=kats
Andrew Sutherland <asutherland@asutherland.org> - Tue, 04 Jun 2019 20:49:34 +0000 - rev 477342
Push 113327 by malexandru@mozilla.com at Wed, 05 Jun 2019 10:00:10 +0000
Bug 1533802 - Sticky nesting for C++, Rust, JS r=kats These are the changes from https://github.com/mozsearch/mozsearch/pull/212 (including the typo fixes requested today. Differential Revision: https://phabricator.services.mozilla.com/D33701
66cee597c19dc2cb3a2e52b0174d701572825312: Bug 1555543 - Adjust scrollbar-apz.css rule so it applies to all scrollbar elements. r=kats
Cameron McCormack <cam@mcc.id.au> - Fri, 31 May 2019 02:10:25 +0000 - rev 476341
Push 113271 by archaeopteryx@coole-files.de at Fri, 31 May 2019 17:09:51 +0000
Bug 1555543 - Adjust scrollbar-apz.css rule so it applies to all scrollbar elements. r=kats Currently it won't match scrollbar elements in HTML documents where the root element has been switched out for something other than <html>, or in shadow trees. Also, move the rule into content.css now that we no longer switch between apz and non-apz versions of this file. Differential Revision: https://phabricator.services.mozilla.com/D33115
63568b2a8178eca237b71cd661e2aaab3b6a360c: Bug 1551735 - Clearly document the case of the RendererOGL receiving a new WebRenderCompositionRecorder while it has one r=kats
Barret Rennie <barret@brennie.ca> - Fri, 31 May 2019 00:31:52 +0000 - rev 476315
Push 113263 by nbeleuzu@mozilla.com at Fri, 31 May 2019 04:08:20 +0000
Bug 1551735 - Clearly document the case of the RendererOGL receiving a new WebRenderCompositionRecorder while it has one r=kats Differential Revision: https://phabricator.services.mozilla.com/D32356
0ef19da1d641b06c3238892d7e81ebc27c85b98d: Bug 1551735 - Record compositions in Web Render r=kats
Barret Rennie <barret@brennie.ca> - Fri, 31 May 2019 00:31:39 +0000 - rev 476314
Push 113263 by nbeleuzu@mozilla.com at Fri, 31 May 2019 04:08:20 +0000
Bug 1551735 - Record compositions in Web Render r=kats Now that we have a suitable composition recorder infrastructure, it is just a matter of plumbing the `WebRenderCompositionRecorder` from the `CompositorBridgeParent` to the `RenderThread` to start recording frames. Differential Revision: https://phabricator.services.mozilla.com/D32234
ced6621fcb1b3e02bb6d5ac4903887760a671c6f: Bug 1551735 - Add a thread-safe composition recorder for WebRender r=kvark,kats
Barret Rennie <barret@brennie.ca> - Fri, 31 May 2019 00:31:24 +0000 - rev 476313
Push 113263 by nbeleuzu@mozilla.com at Fri, 31 May 2019 04:08:20 +0000
Bug 1551735 - Add a thread-safe composition recorder for WebRender r=kvark,kats Since WebRender does its rendering on a separate thread from the compositor thread, we need a composition recorder that can be shared between threads. Differential Revision: https://phabricator.services.mozilla.com/D32231
0c837987a8297e2a1106d4711f6e0e6f2bbb2654: Bug 1551735 - Ref count and document CompositionRecorder r=kats
Barret Rennie <barret@brennie.ca> - Fri, 31 May 2019 00:30:24 +0000 - rev 476309
Push 113263 by nbeleuzu@mozilla.com at Fri, 31 May 2019 04:08:20 +0000
Bug 1551735 - Ref count and document CompositionRecorder r=kats The CompositionRecorder was being stored as a UniquePtr on the CompositorBridgeParent, but was then passed to and stored on the LayerManger as a raw pointer. This has been updated to use a RefPtr. Differential Revision: https://phabricator.services.mozilla.com/D32230
ab8b7c6960e5dd9c3d620e1e20f4abc01ede32ac: Bug 1555379 - Record content paint times for WebRender r=kats
Barret Rennie <barret@brennie.ca> - Thu, 30 May 2019 21:08:01 +0000 - rev 476306
Push 113263 by nbeleuzu@mozilla.com at Fri, 31 May 2019 04:08:20 +0000
Bug 1555379 - Record content paint times for WebRender r=kats The WebRenderBridgeChild now records whether or not it was painting content while sending display lists to the WebRenderBridgeParent, allowing for composition times to be recorded for WebRender. Differential Revision: https://phabricator.services.mozilla.com/D32229