Skip to content

Conversation

@nolanlawson
Copy link
Member

Fixes #222. This change should match Blink's existing behavior and EdgeHTML 16's behavior. See #222 (comment) and #222 (comment) for justification.

index.bs Outdated
holding a number between -1 and the length of the observer's {{IntersectionObserver/thresholds}} property (inclusive).
holding an {{IntersectionObserver}}, a <dfn attribute for=IntersectionObserverRegistration>previousThresholdIndex</dfn> property
holding a number between -1 and the length of the observer's {{IntersectionObserver/thresholds}} property (inclusive), and
a <dfn attribute for=IntersectionObserverRegistration>previousIsIntersecting</dfn> property holding a boolean or <code>undefined</code>.
Copy link
Collaborator

@szager-chromium szager-chromium Aug 28, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we get rid of the "undefined" value for previousIsIntersecting, and just initialize it to "false"? The -1 value for previousThresholdIndex will still serve the purpose of forcing the first notification, so it seems like we can safely make previousIsIntersecting a strict boolean.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! Yes, we can keep it strict boolean.

@szager-chromium szager-chromium merged commit e60d70f into w3c:gh-pages Aug 29, 2017
sideshowbarker pushed a commit to saschanaz/IntersectionObserver that referenced this pull request Mar 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants