1786189 - externally open tab with anchor shows only background color

Status: UNCONFIRMED

(Core :: Graphics: WebRender, defect, P3)

Description

[lilydjwg]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

• start firefox
• from a terminal, run firefox-nightly 'https://bbs.archlinux.org/viewtopic.php?pid=2052581#p2052581'; firefox-nightly 'https://bbs.archlinux.org/viewtopic.php?pid=2052915#p2052915' (these urls are arbitrarily chosen from https://bbs.archlinux.org/search.php?action=show_new&fid=31 for this bug report)
• switch back to firefox, and switch back to the first tab opened.

Actual results:

The page is either only filled with background color (and scrollbar on the right), or the upper half is filled with background. Scrolling will make the page back to normal. The page didn't scroll to anchor automatically.

Expected results:

The page content shows without a manual scroll, and the top should be where the anchor is.

There was similar issues in the past and then fixed. This one is not that old (but at least quite a few days in which I was trying to reproduce it reliably).

I'm on Wayfire (a wlroots-based wayland compositor), Arch Linux with Intel HD 630 graphics card.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Timothy Nikkel (:tnikkel)]

If you can reliable reproduce could you use mozregression to find out what fixed or broke this in the past?

Comment 3

[lilydjwg]

But how can I open a link into mozregression's firefox from command line? Even if I close my own firefox instance and use the firefox binary mozregression put in /tmp, it doesn't work and spawns the profiler manager.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

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

For more information, please visit auto_nag documentation.

Comment 5

[Bob Hood [:bhood]]

Glenn, could you please take a gander at this. Re-categorize if necessary.

Tried the STR on Windows 10 with current m-c, and could not reproduce, so this may be related to Linux driver.

Comment 6

[Timothy Nikkel (:tnikkel)]

This sounds a lot like bug 1720849, which we mostly fixed, but there are still cases of it happening.

I tried to reproduce on macOS, Linux, and Windows but the problem didn't reproduce for me unfortunately.

(In reply to lilydjwg from comment #3)

But how can I open a link into mozregression's firefox from command line? Even if I close my own firefox instance and use the firefox binary mozregression put in /tmp, it doesn't work and spawns the profiler manager.

You can ignore the instance launched by mozregression, but the builds it downloads should be saved locally, for me it's in ~/.mozilla/mozregression/persist. If you take one of those files extract it somewhere and then launch that and use that to try to reproduce (suitable adjusting the command line to point to that binary), does that let you reproduce? It's a fairly manual process, but testing a few builds could help us narrow this down.

Comment 7

[lilydjwg]

Thanks, I've managed to get more information using your method. The widget.gtk.overlay-scrollbars.enabled pref needs to be false to reproduce this bug. I'll narrow down the versions soon.

Comment 8

[lilydjwg]

I have tested with my locally-cached firefox versions, and the results are:

2021-03-01 and later reproduces this issue, from 2020-12-09 to 2021-02-01 the page shows but will not scroll to the anchor, 2020-07-01 and earlier crashes.

I have MOZ_ENABLE_WAYLAND=1 all the time.

Sometimes it takes two or three times to reproduce. Most of time the whole page shows only background color. Very occasionally the top part of the page is not rendered but the bottom part is rendered.

BTW do you know a reliable way to log out my Sync account by manipulating the profile directory files? I sometimes need to copy my profile to reproduce bugs (like this one) but I'm afraid that it would mess up my synced data (because changing all kinds of settings and removing addons).

Comment 9

[Timothy Nikkel (:tnikkel)]

Thanks for testing.

(In reply to lilydjwg from comment #8)

2021-03-01 and later reproduces this issue, from 2020-12-09 to 2021-02-01 the page shows but will not scroll to the anchor, 2020-07-01 and earlier crashes.

So 2021-02-28 doesn't reproduce the issue? Can you run the closest builds that reproduce and don't reproduce and goto about:buildconfig and copy the link there that looks like https://hg.mozilla.org/... then we can see what changed between those builds.

BTW do you know a reliable way to log out my Sync account by manipulating the profile directory files? I sometimes need to copy my profile to reproduce bugs (like this one) but I'm afraid that it would mess up my synced data (because changing all kinds of settings and removing addons).

Sorry I don't know much about sync.

Comment 10

[lilydjwg]

I get this from mozregression:

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f6e71a0eec550054607f5ff7796ae7461dd0189d&tochange=5ff587e0026f2929319cd35e4bed9c76ff2db986

i.e. 2021-02-01 doesn't and 2021-02-02 does. It contains quite a lot of commits though. This was ten months earlier than when I started to use wayland. (This issue doesn't happen with xwayland.)

One detail I might have missed: the Firefox window is placed on another workspace than where I launched those URLs from. It doesn't happen if the Firefox window is covered by the terminal from where I launch new URLs (both of them are maximized).