[M-fis-xorig] High intermittent layout/style/test/test_animations_effect_timing_enddelay.html | OMTA should work
Categories
(Core :: Layout, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox91 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: hiro)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure)
Attachments
(1 file)
Filed by: hikezoe.birchill [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=337395805&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ZbjmqGFSRH-6Em-gJPzQYQ/runs/2/artifacts/public/logs/live_backing.log
| Assignee | ||
Updated•4 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Assignee | ||
Comment 2•4 years ago
|
||
I cloud reproduce the failure locally on an opt build. Will try to catch what's going on there.
| Assignee | ||
Comment 3•4 years ago
|
||
So the failure happens when we haven't received BrowserChild::mTopLevelViewportVisibleRectInBrowserCoords from APZ.
Our animation code has an optimization that we skip restyling/painting where the animation's target element is scrolled out. If the target element is in an OOP iframe, we use the BrowserChild::mTopLevelViewportVisibleRectInBrowserCoords to see whether the iframe is scrolled out (or clipped out) by ancestor viewports. But if we haven't received the mTopLevelViewportVisibleRectInBrowserCoords from APZ, the corresponding function, BrowserChild::GetTopLevelViewportVisibleRectInBrowserCoords returns an empty rectangle, thus we incorrectly consider the element is scrolled out, then we fail to paint the animation, thus we fail a sanity check in animation_utils.js.
| Assignee | ||
Comment 4•4 years ago
|
||
With this change we no longer incorrectly consider there is no visible rect for
the OOP iframe where we haven't yet received the rectangle from APZ.
Comment 6•4 years ago
|
||
| bugherder | ||
Description
•