-
Notifications
You must be signed in to change notification settings - Fork 902
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
md-tabs: scroll to active tab on init shouldn't be smooth behaviour #5497
Closed
kkachniarz220 opened this issue
Feb 27, 2024
· 1 comment
· Fixed by #5487 or joepdooper/ivy#9 · May be fixed by X-oss-byte/pigweed#61, X-oss-byte/pigweed#70 or X-oss-byte/pigweed#73
Closed
md-tabs: scroll to active tab on init shouldn't be smooth behaviour #5497
kkachniarz220 opened this issue
Feb 27, 2024
· 1 comment
· Fixed by #5487 or joepdooper/ivy#9 · May be fixed by X-oss-byte/pigweed#61, X-oss-byte/pigweed#70 or X-oss-byte/pigweed#73
Comments
copybara-service bot
pushed a commit
that referenced
this issue
Feb 27, 2024
Fixes #5497 PiperOrigin-RevId: 610802319
Looks like the boolean logic was flipping and we were smooth scrolling on init and instant scrolling on arrow key navigation, whoops! I'm fixing this in #5499. It'll also fix setting |
copybara-service bot
pushed a commit
that referenced
this issue
Feb 27, 2024
Fixes #5497 PiperOrigin-RevId: 610802319
copybara-service bot
pushed a commit
that referenced
this issue
Feb 28, 2024
Fixes #5497 PiperOrigin-RevId: 610802319
Merged
This was referenced May 18, 2024
This was referenced Jul 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is affected?
Component
Description
Scrolling to active tab on component init should be immediate, now it is smooth.
In addition there is weird behaviour with playground:
screen-capture.9.webm
Reproduction
lit.dev
Workaround
I have not found a reproduction
Is this a regression?
No or unsure. This never worked, or I haven't tried before.
Affected versions
1.3.0
Browser/OS/Node environment
Chrome 121.0.6167.187
Windows 11
The text was updated successfully, but these errors were encountered: