Japanese articles on PS blog cannot be scrolled normally
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect)
Tracking
()
People
(Reporter: averageos2, Unassigned)
References
(Regression)
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0
Steps to reproduce:
I tried to browse the Japanese article on the PS blog
https://blog.ja.playstation.com/2021/09/27/20210927-indies/
Actual results:
When I try to scroll the article, a blank line occurs in the article and I can't scroll to the second half of the article forever.
https://blog.ja.playstation.com/2021/09/27/20210927-indies/
Expected results:
It means that you can scroll without creating blank lines. It did not occur in Firefox 72 ESR.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Panning and Zooming' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
I get this regression range
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ee89deeb4fb6d12456c551c5ab4aaae151ceedae&tochange=83895192ba27f0ae37ee27eb9524fb4a46bcf3a5
The only thing that seemed like it could maybe be responsible is bug 1650715, so I tried to flip the pref layout.css.image-orientation.initial-from-image to false (you need to run an old build, the pref has since been removed) and that does indeed fix it for me. Still not sure what's going on.
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Note that disabled scroll anchoring or lazy load images does not fix the issue.
![]() |
||
Comment 4•4 years ago
•
|
||
After the image is displayed, continue scroll down to create a blank area. Also, scrolling upward after scrolling to the bottom will result in a blank area.
This blank area will not be re-rendered.
I got a different recession range than comment#2.
#1 Regression window with clean profile):
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=69ae5f925fbc67d86a6fda1ed0a4b02ae8fc4588&tochange=02d875d4f7d769cd03be3175490377dc600355fe
Regressed by: Bug 1676966
#2 Regression window(Even if gfx.font_rendering.fallback.async = false ):
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5a74388d847a9487593a0fe28a706015ac353220&tochange=365bfc91ddd5d9be1a5d5bee72377c025b099321
Regressed by: Bug 1708590
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Interesting that we are seeing different regression windows, seems like it might have something to do with reflow, maybe timing related? That could explain why we get those different windows.
![]() |
||
Comment 6•4 years ago
|
||
(In reply to Timothy Nikkel (:tnikkel) from comment #5)
Interesting that we are seeing different regression windows, seems like it might have something to do with reflow, maybe timing related? That could explain why we get those different windows.
Yes, right. Scrolling fast enough caused the problem. And I got a same range of comment #2.
![]() |
||
Comment 7•4 years ago
|
||
Workaround,
Changing position:sticky
of shear buttons to static seems to prevent unexpected reflow.
.post-like-share {
position: static !important
}
Comment 8•4 years ago
|
||
The severity field is not set for this bug.
:boris, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 9•4 years ago
|
||
This looks the same as bug 1747024, and dholbert has an analysis in bug 1747024 comment 9.
Description
•