Closed Bug 1701547 Opened 4 years ago Closed 3 years ago

Do not apply nsChangeHint_RepaintFrame for background color animations on the root element (and the body) (or run the background color animations on the compositor)

Categories

(Core :: DOM: Animation, defect)

Product:
Core
Component:
DOM: Animation
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1699890

People

(Reporter: hiro, Unassigned)

References

Details

We basically run background color animations on the compositor thread, but it's only for nsDisplayBackgroundColor display items, not for nsDisplayCanvasBackgroundColor nor for nsDisplaySolidColor (I am not sure which one is used for the root element).

So background color animations on the root element don't run on the compositor, then unfortunately we misbehave in AddLayerChangesForAnimation that even if there is no change hint differences we forcibly apply nsChangeHint_RepaintFrame, thus we repeatedly receive MozAfterPaint events in the wpt reftest harness (bug 1701128).

We should avoid it, or run the background color on the compositor as well as other elements.

See Also: → 1701128
Summary: Do not apply nsChangeHint_RepaintFrame for background color animations on the root element (or run the background color animations on the compositor) → Do not apply nsChangeHint_RepaintFrame for background color animations on the root element (and the body) (or run the background color animations on the compositor)

This will be fixed by D115774 (which is for bug 1699890). Once it landed I am going to close this bug as a dup of bug 1699890.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.