-
Notifications
You must be signed in to change notification settings - Fork 22.4k
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
Issue with "ScrollToOptions.behavior": Description of auto
value is wrong, lacking historical instant
value
#2719
Comments
auto
value is wrong.auto
value is wrong, lacking historical instant
value
I've noticed there's also an undocumented In this email list, it's seems firefox implmented
|
the value |
but browsers treat them as different behavior (might for backward compatible reason). |
mdn now reflects "instant" as an allowed option but i'm seeing no mention of it in the the spec linked there apart from being the previous name for auto. should it be on mdn as gospel? i want to have an instant option, but it seems premature to have it on that page unless i'm not looking at the right spec doc. |
These spec won't address behaviors on historical or living browsers that might not match with its expecting standard, that's why the mdn should hint this point. |
* Update behavior parameter Fixes #2719 * Add intro sentence * Update files/en-us/web/api/window/scroll/index.md Co-authored-by: Joshua Chen <sidachen2003@gmail.com> Co-authored-by: Joshua Chen <sidachen2003@gmail.com>
MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/ScrollToOptions/behavior
What information was incorrect, unhelpful, or incomplete?
The
behavior: 'auto'
will not always do an instant scroll that jumps to the element as described in the doc.Specific section or headline?
https://developer.mozilla.org/en-US/docs/Web/API/ScrollToOptions/behavior#value
What did you expect to see?
Did you test this? If so, how?
Norserium/react-indiana-drag-scroll#53 (comment)
MDN Content page report details
en-us/web/api/scrolltooptions/behavior
The text was updated successfully, but these errors were encountered: