Closed Bug 987005 Opened 10 years ago Closed 10 years ago

Add comments to the condition in PopThebesLayerData() that decides whether we want to optimize a thebes layer to an image or color layer

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla31

People

(Reporter: mstange, Assigned: mstange)

Details

Attachments

(1 file, 1 obsolete file)

The condition

> if (isRetained && (data->mIsSolidColorInVisibleRegion || imageContainer) &&
>     (data->mLayer->GetValidRegion().IsEmpty() || mLayerBuilder->CheckInLayerTreeCompressionMode())) {

completely went over my head when I read it the first time, and I had to do some extended bugzilla archeology in order to understand it completely. Some comments would be very helpful. This patch adds them.
Attachment #8395505 - Flags: review?(roc)
Comment on attachment 8395505 [details] [diff] [review]
document-optimization-to-color-or-image-layer

Review of attachment 8395505 [details] [diff] [review]:
-----------------------------------------------------------------

::: layout/base/FrameLayerBuilder.cpp
@@ +1896,5 @@
>    nsRefPtr<Layer> layer;
>    nsRefPtr<ImageContainer> imageContainer = data->CanOptimizeImageLayer(mBuilder);
>  
> +  if ((aData->mIsSolidColorInVisibleRegion || imageContainer) &&
> +      ShouldOptimizeAwayThebesLayer(data, mLayerBuilder)) {

Name it "CanOptimizeAwayThebesLayer"
Attachment #8395505 - Flags: review?(roc) → review+
Attached patch v2Splinter Review
Attachment #8395505 - Attachment is obsolete: true
https://hg.mozilla.org/mozilla-central/rev/94df6fc66986
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla31
You need to log in before you can comment on or make changes to this bug.