-
Notifications
You must be signed in to change notification settings - Fork 522
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
[IntersectionObserver] #295 V2: visibility detection #523
Merged
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This implies the value
false
iftrackVisibility
isfalse
, while later on the algorithm is specified to immediately returnstrue
in that case. Of the two,false
has a safer failure mode if someone thinks they're tracking visibility but they screwed up somewhere. Either way, the two parts of the spec need to agree.Even better would be if
isVisible
were completely undefined if you had not enabledtrackVisibility
.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.
For the purpose of feature detection, how about setting
isVisible
tonull
iftrackVisibility
is false? I think that's also more consistent with other IDL I have seen.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.
you can't set a boolean to null, can you? Honest question -- I'm not sure what the WebIDL can express, nor what would be most consistent with similar APIs. This feels kind of off, but a permanent
false
when tracking isn't enabled wouldn't be terrible. Thetrue
specified in the algorithm below will lead to trouble.Any thoughts, @annevk or @zcorpan?
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.
I'm not an IDL expert, but for the record chromium's IDL code generator allows null-able booleans. I wrote a chromium patch which would implement the behavior I proposed, and it works.
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.
You can have nullable booleans (the IDL of this PR does not do that btw), but generally it would be better to use an enum.
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.
I'm not sure an enum will work here, because we need two different values that will evaluate to
false
when cast to boolean.If there are no objections, I'll just make it a permanent
false
when tracking isn't enabled. I think that's probably what we want from a developer ergonomics no-surprises point of view. Feature detection can always be done viaIntersectionObserverEntry.prototype.hasOwnProperty('isVisible')
.