-
Notifications
You must be signed in to change notification settings - Fork 532
Issues: w3c/IntersectionObserver
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Sanity check that knowing cross-domain iframes' position doesn't leak security information
#19
by ojanvafai
was closed Sep 8, 2015
It's not clear what the use-case is for thresholdCallbacks: false
#18
by ojanvafai
was closed Sep 8, 2015
Figure out how to enforce that observed element is a descendant of the viewport element
duplicate
needs spec
#16
by ojanvafai
was closed Nov 20, 2015
What should happen if the viewport-defining element is an inline?
needs spec
#13
by ojanvafai
was closed Mar 26, 2018
MS Feedback: Is the PositionObserver intended for Inline elements?
#10
by travisleithead
was closed Sep 8, 2015
MS Feedback: Please don't expose the paint-rect (viewportPaintRect)
#8
by travisleithead
was closed Aug 11, 2015
MS Feedback: Usage for Ad Impression Usage Scenario (what is importance for into/out-of view)?
#6
by travisleithead
was closed Sep 8, 2015
MS Feedback: Delay loading scenario applicability questioned
#5
by travisleithead
was closed Sep 8, 2015
MS Feedback: Alternative Idea: imperative and event-based
#4
by travisleithead
was closed Sep 8, 2015
MS Feedback: Data scrollers (List view) scenario likely not in scope
#3
by travisleithead
was closed Sep 8, 2015
Provide Microsoft Edge-team feedback on PositionObserver
#2
by travisleithead
was closed Sep 8, 2015
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.