Closed
Bug 1662277
Opened 5 years ago
Closed 5 years ago
IntersectionObserverEntry objects should have a consistent time with everything else in the same refresh driver tick / update the rendering steps
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
82 Branch
| Tracking | Status | |
|---|---|---|
| firefox82 | --- | fixed |
People
(Reporter: sefeng211, Assigned: emilio)
References
()
Details
Attachments
(2 files)
https://searchfox.org/mozilla-central/rev/0c682c4f01442c3de0fa6cd286e9cadc8276b45f/dom/base/Document.cpp#15095 should use the now timestamp which is at the beginning of the refresh driver.
Flags: needinfo?(emilio)
| Reporter | ||
Updated•5 years ago
|
Summary: for IntersectionObserverEntry objects having a consistent time with everything else → IntersectionObserverEntry objects should have a consistent time with everything else
| Assignee | ||
Updated•5 years ago
|
Flags: needinfo?(emilio)
Summary: IntersectionObserverEntry objects should have a consistent time with everything else → IntersectionObserverEntry objects should have a consistent time with everything else in the same refresh driver tick / update the rendering steps
| Assignee | ||
Comment 1•5 years ago
|
||
So this does indeed show the same timestamps in rAF callbacks and IntersectionObserver in WebKit trunk, but not in Blink or current Epiphany at least.
| Assignee | ||
Comment 2•5 years ago
|
||
This is per spec, see the link in the test. I wouldn't see much point on
doing this for IntersectionObserver on its own, see:
https://bugzilla.mozilla.org/show_bug.cgi?id=1518999#c28
Though I see the point of doing this for the paint timing API, and I
guess for consistency we should do it here too.
Updated•5 years ago
|
Assignee: nobody → emilio
Status: NEW → ASSIGNED
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d23c9b17da6b
Make IntersectionObserver entries have the same timestamp as other timestamp-returning things during the "update the rendering steps". r=sefeng
Comment 4•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•