Closed Bug 1733048 Opened 4 years ago Closed 4 years ago

Japanese articles on PS blog cannot be scrolled normally

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

Firefox 94
defect

Tracking

()

RESOLVED DUPLICATE of bug 1747024

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.

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.

Component: Untriaged → Panning and Zooming
Product: Firefox → Core

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.

Status: UNCONFIRMED → NEW
Component: Panning and Zooming → Layout: Images, Video, and HTML Frames
Ever confirmed: true
Regressed by: 1650715
Has Regression Range: --- → yes

Note that disabled scroll anchoring or lazy load images does not fix the issue.

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

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.

(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.

Workaround,
Changing position:sticky of shear buttons to static seems to prevent unexpected reflow.

.post-like-share {
    position: static !important
}

The severity field is not set for this bug.
:boris, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(boris.chiou)
Severity: -- → S3
Flags: needinfo?(boris.chiou)

This looks the same as bug 1747024, and dholbert has an analysis in bug 1747024 comment 9.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.