scroll-behavior: smooth not working in firefox nightly
Categories
(Core :: CSS Transitions and Animations, defect)
Tracking
()
People
(Reporter: asunada, Unassigned)
References
(Regression)
Details
(Keywords: regression)
In firefox scroll-behavior is working just fine when jumping from one part of the page to another via anchor tag.
In firefox nightly, scroll-behavior is just abruptly jumping from one page to the other as if nothing changed.
Firefox: https://drive.google.com/open?id=12suTUL8diD2JXg-QWn-u_sSEOhH4oy6l
Firefox nightly: https://drive.google.com/open?id=1snJoQwzevMCqL7HqVgb49dz1URERWH4f
Comment 1•6 years ago
|
||
From the video this looks from https://people.mozilla.org? It looks like it's using scroll-behavior: smooth
but the scroll container is the <html>
rather than the <body>
. This is a regression from bug 1560237, and I suspect it's WONTFIX. It doesn't seem to be working in other browsers either.
You should add scroll-behavior: smooth
to the <html>
, not the <body>
element.
Updated•6 years ago
|
Reporter | ||
Comment 2•6 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #1)
From the video this looks from https://people.mozilla.org? It looks like it's using
scroll-behavior: smooth
but the scroll container is the<html>
rather than the<body>
. This is a regression from bug 1560237, and I suspect it's WONTFIX. It doesn't seem to be working in other browsers either.You should add
scroll-behavior: smooth
to the<html>
, not the<body>
element.
Yes this is from https://people.mozilla.org!
Changing the scroll-behavior rule to be in the html tag definitely fixed the issue. Thank you for that touch! It helped me with my story.
However, this is still an issue with scroll-behavior as this behavior works as expected in the standard firefox. You can run your own tests on people.mozilla.org in both firefox and firefox nightly on the profile page and see the behavior difference too!
Comment 3•6 years ago
|
||
Yeah, my point is that this was an intentional behavior change in bug 1560237. Before, having that on the <body>
caused the <body>
styles to be propagated to the viewport, which was against the spec and didn't match other browsers.
Reporter | ||
Comment 4•6 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #3)
Yeah, my point is that this was an intentional behavior change in bug 1560237. Before, having that on the
<body>
caused the<body>
styles to be propagated to the viewport, which was against the spec and didn't match other browsers.
Oh fascinating! Cool, thanks for the explanation!
Updated•3 years ago
|
Description
•