032ba47c66844cb8717ff954539e2707e655c178: Bug 1022612. Part 21: Remove DidComputeVisibility checking. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:48:01 +1200 - rev 214810
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 21: Remove DidComputeVisibility checking. r=mattwoodrow
2f6cb0f412f7e6bd0c76acf6820734f06b7ae640: Bug 1022612. Part 20: Do the business. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:48:01 +1200 - rev 214809
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 20: Do the business. r=mattwoodrow
b4b6049145dcca3aef82b3514cf023d5c5b458b7: Bug 1022612. Part 19: Test that merged display item lists merge their contents in the correct z-order. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 07 Jul 2014 17:46:29 +1200 - rev 214808
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 19: Test that merged display item lists merge their contents in the correct z-order. r=mattwoodrow Prior to this patch, the only tests that caught this were a couple of obscure cases on B2G. This test tests it on all platforms.
376c45f4d905aff7b1f4161fd6bf8a52c7b286ba: Bug 1022612. Part 18: When ComputeVisibility returns false, RecomputeVisibility should avoid painting the item. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Fri, 20 Jun 2014 17:24:31 +1200 - rev 214807
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 18: When ComputeVisibility returns false, RecomputeVisibility should avoid painting the item. r=mattwoodrow
549e3cb9e1118b1e26d48e3d637c961c51644380: Bug 1022612. Part 17: RecordFrameMetrics should not set layer visible regions. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Wed, 11 Jun 2014 23:12:14 +1200 - rev 214806
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 17: RecordFrameMetrics should not set layer visible regions. r=mattwoodrow This is unnecessary. FrameLayerBuilder sets the correct region.
c59ee68b19179b55cd9264817e6478698071e7a2: Bug 1022612. Part 16: No need to exclude final transparent region from window opaque region. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:48:01 +1200 - rev 214805
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 16: No need to exclude final transparent region from window opaque region. r=mattwoodrow The removed code should be a no-op as long as the window opaque region is accurate enough.
e95971991caa55a4f82570a47dce84ffb64e48f0: Bug 1022612. Part 14: Don't compute a final transparent region anymore. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:48:00 +1200 - rev 214804
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 14: Don't compute a final transparent region anymore. r=mattwoodrow Computing this via FrameLayerBuilder is some work and we don't really have to. SuppressComponentAlpha will be true in more cases. This will be OK as long as text in the chrome window is over opaque content in the same ThebesLayer. We will miss some edge cases such as text in 'opacity' with no opaque background. This should be OK.
121bf69509b1ed83e8b8153f55ba5c6c6276c146: Bug 1022612. Part 13: Set mDidComputeVisibility in ProcessDisplayItems. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 07 Jul 2014 17:46:28 +1200 - rev 214803
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 13: Set mDidComputeVisibility in ProcessDisplayItems. r=mattwoodrow
cc140abf7b17677cd186c65d893887f5184f83e3: Bug 1022612. Part 12: Propagate NeedsTransparentSurface in ProcessDisplayItems. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:48:00 +1200 - rev 214802
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 12: Propagate NeedsTransparentSurface in ProcessDisplayItems. r=mattwoodrow
75fffcce9c4d66a33722673943b93abebae42e46: Bug 1022612. Part 11: Set opaque flag on nsDisplayList if we find an opaque item that covers the whole list. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:48:00 +1200 - rev 214801
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 11: Set opaque flag on nsDisplayList if we find an opaque item that covers the whole list. r=mattwoodrow This is less general than what nsDisplayItem::ComputeVisibility does. This means if multiple opaque items together cover the list bounds, but not individually, we won't mark the list as opaque. I think that should be OK.
3bf33a32bfe0b3250acb3e4bfb68ae6525884c7b: Bug 1022612. Part 10: Implement merging and flattening in ProcessDisplayItems. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:48:00 +1200 - rev 214800
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 10: Implement merging and flattening in ProcessDisplayItems. r=mattwoodrow BuildContainerLayerFor now has to be able to mutate the passed-in display item list.
e4e2a1dcadc8eb34ca162155534aa330c71efa26: Bug 1022612. Part 9: nsDisplayScrollInfoLayer destructor does not need to destroy ScrollLayerCount. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:47:59 +1200 - rev 214799
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 9: nsDisplayScrollInfoLayer destructor does not need to destroy ScrollLayerCount. r=mattwoodrow Getting the timing of this right without processing display items in reverse order is hard. But it doesn't matter if this property sticks around anyway.
5ebd2f6b65a6ca6553c587420210c4124bff76d3: Bug 1022612. Part 8: nsDisplayWrapList (but not subclasses) should return true for ShouldFlattenAway. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:47:59 +1200 - rev 214798
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 8: nsDisplayWrapList (but not subclasses) should return true for ShouldFlattenAway. r=mattwoodrow Also the assertion in TryMerge is going away because we're going to do TryMerge first in FrameLayerBuilder.
b81f9a774059dd77b7ede60c5b656e1f3f9a0a6c: Bug 1022612. Part 7: Enable APZC for IPC reftests. r=billm
Robert O'Callahan <robert@ocallahan.org> - Wed, 25 Jun 2014 18:38:05 +1200 - rev 214797
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 7: Enable APZC for IPC reftests. r=billm
1ad096055f1d1d15a339fbe9e82edcf25a12ef74: Bug 1022612. Part 6: Set the initial mVisibleRect for each display item to the dirty rect when we create the item. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:47:59 +1200 - rev 214796
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 6: Set the initial mVisibleRect for each display item to the dirty rect when we create the item. r=mattwoodrow
6d2fc524e961188e589a7a1bc15ec23be28d2d21: Bug 1022612. Part 5: BuildDisplayListForExtraPage needs to pass the correct dirty rect in. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Mon, 09 Jun 2014 16:47:58 +1200 - rev 214795
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 5: BuildDisplayListForExtraPage needs to pass the correct dirty rect in. r=mattwoodrow When printing, every page has the same origin. So doing this change naively would result in the first page having all the display items for every page added to it, and all but the first page's display items being pruned away by PruneDisplayListForExtraPage. This would making printing long documents very slow. We avoid that problem with the new check for NS_FRAME_FORCE_DISPLAY_LIST_DESCEND_INTO, so the only pages other than the current page we descend into are the ones with placeholders for abs-pos content on the current page.
cdaa916f6851fe278d16c48ce41b021c3cb8d421: Bug 1022612. Part 4: Track current dirty rect in nsDisplayListBuilder. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Tue, 20 May 2014 15:59:14 +1200 - rev 214794
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 4: Track current dirty rect in nsDisplayListBuilder. r=mattwoodrow We need this to set the initial visible rect during display list construction. Eventually we'll also be able to get rid of the dirty rect parameter to nsIFrame::BuildDisplayList.
18ffe0bb4d423f92be35a11d4bc4d09280ebb089: Bug 1022612. Part 3: Rename "cached frame" to "current frame" in nsDisplayListBuilder and take advantage of the fact it's always set. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Tue, 20 May 2014 15:49:54 +1200 - rev 214793
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 3: Rename "cached frame" to "current frame" in nsDisplayListBuilder and take advantage of the fact it's always set. r=mattwoodrow
4e502d50b8e1761e1d9fec4ed2ae7d2025b12166: Bug 1022612. Part 2: Remove unused nsDisplayWrapList constructor. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Tue, 20 May 2014 15:08:20 +1200 - rev 214792
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 2: Remove unused nsDisplayWrapList constructor. r=mattwoodrow
e5bacdd4594c4e86997ca37d417c1d2a92da55b2: Bug 1022612. Part 1: Always pass a frame to AutoBuildingDisplayList. r=mattwoodrow
Robert O'Callahan <robert@ocallahan.org> - Tue, 20 May 2014 15:08:18 +1200 - rev 214791
Push 3857 by raliiev@mozilla.com at Tue, 02 Sep 2014 16:39:23 +0000
Bug 1022612. Part 1: Always pass a frame to AutoBuildingDisplayList. r=mattwoodrow
(0) -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip