FrameLayerBuilder calls frame->AddStateBits(NS_FRAME_PAINTED_THEBES) before it calls item->Paint(): https://searchfox.org/mozilla-central/rev/c5ba0f076697d8a6f4548f821b1d97c267ad207c/layout/painting/FrameLayerBuilder.cpp#6009-6012 This is what makes reftest-no-paint work. We should do the same thing in the two places in WebRenderCommandBuilder where we call nsDisplayItem::Paint, in order to benefit from existing invalidation tests and so that we can add new tests if we encounter any invalidation bugs, for example with blob invalidation.
10 months ago
Priority: -- → P1
9 months ago
status-firefox61: affected → disabled
This isn't directly user-facing, downgrading from P1.
Priority: P1 → P2
Created attachment 9005283 [details] [diff] [review] Hook up invalidation testing in WebRender
Attachment #9005283 - Flags: review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/3cf0bec611e1 Hook up invalidation testing in WebRender. r=mstange
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/77fa43334879 Hook up invalidation testing in WebRender. r=mstange
Status: NEW → RESOLVED
Last Resolved: 5 months ago
status-firefox63: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.