The reftest harness doesn't take the latest snapshot if reftest-no-flush is specified
Categories
(Testing :: Reftest, defect, P3)
Tracking
(firefox77 wontfix, firefox78 wontfix, firefox79 wontfix, firefox80 fixed)
People
(Reporter: hiro, Assigned: hiro)
References
Details
Attachments
(2 files)
Because there is no MozAfterPaint fired by changes for animations on the compositor.
It seems to have been regressed since bug 1349991.
Assignee | ||
Comment 1•5 years ago
|
||
Attaching file is a patch containing a reftest you can see the issue.
The testing HTML has a transform animation runs on the compositor. When you run the reftest locally, you will see a big green circle moves downward, but if you see the reftest failure log on the reftest analyzer, you will see that the green circle is positioned at the initial place. That's because we never call SendUpdateCanvasForEvent after we took the initial snapshot because there is no MozAfterPaint events.
Assignee | ||
Comment 2•5 years ago
|
||
Presumably to fix this issue, we need to set updateCanvasPending to true and set updateCanvasRects to the whole area after "reftest-wait" is removed if reftest-no-flush is specified.
Assignee | ||
Comment 3•5 years ago
|
||
Interestingly I can observe MozAfterEvents by compositor animations on non-E10S. :)
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
That's because we no longer fire MozAfterPaint event for changes by
animations on the compositor.
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
I had blocked a wrong bug. :)
Updated•5 years ago
|
Comment 8•5 years ago
|
||
bugherder |
Comment 9•5 years ago
|
||
The patch landed in nightly and beta is affected.
:hiro, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•5 years ago
|
Description
•