-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[intersection-observer] Test isIntersecting change events #7215
[intersection-observer] Test isIntersecting change events #7215
Conversation
There are no owners for this pull request. Please reach out on W3C's irc server (irc.w3.org, port 6665) on channel #testing (web client) to get help with this. Thank you! |
Build PASSEDStarted: 2017-08-31 22:18:01 Failing Jobs
View more information about this build on: |
@tobytailor Are you able to review this? |
w3c-test:mirror |
@scottlow @szager-chromium are you able to review this? @nolanlawson can you rebase it so that Travis runs again? |
e4bf8a3
to
25c616d
Compare
rebased ^ |
w3c-test:mirror |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manually confirmed http://w3c-test.org/submissions/7215/intersection-observer/isIntersecting-change-events.html to be passing in Chrome, Edge and Firefox. Safari fails with "Can't find variable: IntersectionObserver"
This is a test for the change introduced in w3c/IntersectionObserver#245. The main difference with the previous version of the spec is that the observer fires events when
isIntersecting
changes butthresholdsIndex
does not, which covers some odd edge-adjacency scenarios.On my machine, Chrome 60 and Edge 16 prerelease (e.g. public insider 16275) pass the 5 new tests, whereas Firefox Nightly (57.0a1 2017-08-31) does not. This is to be expected given discussion in w3c/IntersectionObserver#222.
/cc @szager-chromium @tobytailor @scottlow