You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, been taking advantage of scroll-behavior: smooth, but when either using a supporting browsers forward/back buttons or programmatically interacting with the history interface, the property/behavior isn't respected, always showcasing what would be the auto (or the old instant) value.
The spec says...
The scroll-behavior property specifies the scrolling behavior for a scrolling box, when scrolling happens due to navigation or CSSOM scrolling APIs
I could interpret that as meaning the behavior seen in browsers are issues with implementation, but I'm not sure. And if so, could the spec be clearer so that if a clicked "jumplink" exhibits support for the scroll-behavior property, then that same behavior would be respected if the user clicks back/forwards or performs an action that manipulates the history interface?
The text was updated successfully, but these errors were encountered:
@annevk I see you were a previous editor on this module, that currently has no editor. If you have any insights, especially if this is solely implementations not adhering to the specification, I can close this and file reports with each vendor.
It's probably worth keeping this open until it's covered by the test suite somehow. You're correct that these are bugs (history traversal == navigation). If you file bugs, please link them from here.
https://drafts.csswg.org/cssom-view-1/#propdef-scroll-behavior
Recently, been taking advantage of
scroll-behavior: smooth
, but when either using a supporting browsers forward/back buttons or programmatically interacting with the history interface, the property/behavior isn't respected, always showcasing what would be theauto
(or the oldinstant
) value.The spec says...
I could interpret that as meaning the behavior seen in browsers are issues with implementation, but I'm not sure. And if so, could the spec be clearer so that if a clicked "jumplink" exhibits support for the scroll-behavior property, then that same behavior would be respected if the user clicks back/forwards or performs an action that manipulates the history interface?
The text was updated successfully, but these errors were encountered: