Closed
Bug 1529389
Opened 5 years ago
Closed 5 years ago
add a test for IntersectionObserverEntry.isIntersecting
Categories
(Core :: Layout, enhancement, P3)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla67
Tracking | Status | |
---|---|---|
firefox67 | --- | fixed |
People
(Reporter: heycam, Assigned: heycam)
Details
(Keywords: dev-doc-needed)
Attachments
(1 file)
This is an interop issue between Chrome and Firefox. It looks like Firefox is following the spec and Chrome is not. It also looks like the MDN docs are out of date.
https://www.reddit.com/r/firefox/comments/asrsus/why_does_this_doesnt_work_on_firefox_correctly/
Assignee | ||
Comment 1•5 years ago
|
||
Assignee | ||
Comment 2•5 years ago
|
||
(In reply to Cameron McCormack (:heycam) from comment #0)
It also looks like the MDN docs are out of date.
Specifically in the Thresholds section of https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API it talks about how isIntersecting
takes the threshold into account, but actually it should be set to true or false just based on whether there is any intersection (or adjacency) at all, regardless of the threshold.
Pushed by cmccormack@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e291cb4e39c7 Add a WPT for IntersectionObserverEntry.isIntersecting. r=dholbert
Comment 4•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/15545 for changes under testing/web-platform/tests
Upstream PR merged
You need to log in
before you can comment on or make changes to this bug.
Description
•