-
Notifications
You must be signed in to change notification settings - Fork 521
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
Clarify whether QueuedEntries should be cleared on unobserve/disconnect
TPAC2019
#356
opened Apr 12, 2019 by
alijuma
Dependency on undefined behavior via getBoundingClientRect()
external-dependency
#398
opened Oct 29, 2019 by
frivoal
What to do with threshold values other than 1 when trackVisibility is requested?
v2
#412
opened Feb 11, 2020 by
szager-chromium
Allow setting a root to be the screen rather than the page viewport
#471
opened May 11, 2021 by
chrishtr
overflow-clip-margin or overflow-clip along one axis only on root or target
#518
opened Oct 31, 2023 by
wangxianzhu
Specify lifetime of the targets of a IntersectionObserver instance
#520
opened Dec 20, 2023 by
xeaone
The Compute the Intersection algorithm has a link to the wrong spec.
#527
opened Nov 21, 2024 by
Psychpsyo
Specify that observer.thresholds should be a frozen array
needs test
#162
opened Oct 13, 2016 by
ziyunfei
Should the default value of thresholds be changed for consistency?
tpac2017
#164
opened Oct 17, 2016 by
rjgotten
"While container is not the intersection root:" doesn't make sense
#196
opened Feb 9, 2017 by
smaug----
rootMargin may need to be directionally sensitive
i18n-needs-resolution
Issue the Internationalization Group has raised and looks for a response on.
tpac2017
#259
opened Oct 5, 2017 by
r12a
Provide cross-origin rootBounds and rootMargin with frame-level opt-in
v2
#280
opened Jan 24, 2018 by
ojanvafai
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.