Closed Bug 1692519 Opened 3 years ago Closed 3 years ago

Library menu is glitchy when opening or closing submenus


(Core :: Graphics, defect, P3)




Tracking Status
firefox-esr78 --- unaffected
firefox85 --- unaffected
firefox86 --- unaffected
firefox87 - affected
firefox88 --- affected
firefox89 --- affected


(Reporter: florencia.diciocco, Unassigned)



(Keywords: steps-wanted)


(3 files)

[Affected platforms:]
Windows 10
Ubuntu 20

[Affected versions:]
Nightly 87.0a1

when I browse through the library menu (in the toolbar), the menu is glitchy.


  1. Open Firefox with a new profile.
  2. Have the library menu on the toolbar.
  3. Open one of the subfolders.
  4. Go back to the main menu.

[Actual result:]
The menu is glitchy when changing the box's size.

[Expected result:]
The menu shouldn't be glitchy.

Moving across to menus, since it seems this was affected by the recent proton work. Clearing severity so that it can get triaged.

Severity: S3 → --
Group: firefox-core-security, mozilla-employee-confidential

Why is this marked as confidential? I don't see any personal data here

Flags: needinfo?(fdiciocco)
Component: Bookmarks & History → Menus

Hi Marco sorry for the confusion, I marked it as such because of the Screen Recording. It slightly showed some new design for the Library Menu.

Flags: needinfo?(fdiciocco)

We don't need to mark bugs as confidential.

Can you clarify if this is happening without setting any proton preferences?

Group: mozilla-employee-confidential, firefox-core-security
Flags: needinfo?(fdiciocco)

(Also, if not impacted by proton preferences, please can you find a regression window? Thank you.)

(In reply to :Gijs (he/him) from comment #4)

We don't need to mark bugs as confidential.

Can you clarify if this is happening without setting any proton preferences?

This happens both with and without preferences.

(In reply to :Gijs (he/him) from comment #5)

(Also, if not impacted by proton preferences, please can you find a regression window? Thank you.)

I tried but for some weird reason, on the mozregression I couldn't replicate this bug.

Flags: needinfo?(fdiciocco)

[Tracking Requested - why for this release]:
If this is happening even without proton we need to get to the bottom of what broke and how?

This sounds like it's related to some kind of graphics setting. Can you reproduce in a completely clean profile during the first run? Or perhaps only the second run? We'll need to nail down what is triggering this in order to figure out how this is happening.

:dholbert, I don't suppose you have ideas about what is going on here based on the video / not being able to reproduce on mozregression?

Flags: needinfo?(fdiciocco)
Flags: needinfo?(dholbert)
Keywords: steps-wanted

I also tried to reproduce this issue again, In our latest builds as well as the older builds including the one where this issue was logged from but I couldn't reproduce it anymore, It used to happen with some fresh profiles but not every time, I'm not exactly sure what is causing it but I will keep trying some of the older builds.

Unfortunately the Mozregression tool is blocked by our AV plus with the older mozregression tool build i.e version 4.0.5 that does work the Nightly builds from 2021 do not open because of the Troubleshoot Compatibility issue, so we have to manually download and test each version.

I ran mozregression and ended up to a WebRender patch (Bug 1574746) as the culprit. Disabling WR does indeed prevent this issue.

(In reply to tgn-ff from comment #9)

I ran mozregression and ended up to a WebRender patch (Bug 1574746) as the culprit. Disabling WR does indeed prevent this issue.

I'm a little confused because QA reported this as a new bug in 87, and that patch landed in 78. I cannot reproduce the issue shown in the video at all myself.

Is it perhaps the case that webrender is default-on in nightly but not release builds (where the set of people for which it's turned on is smaller, but not empty), and this issue only happens with webrender on?

I also wonder if this is related to bug 1687828 (which I think was really a dupe of bug 940733 which we should probably close) - but that'd mean 86 is affected, too.

Mike, do you have ideas on what's going on here?

Flags: needinfo?(mconley)

I can reproduce the issue on ESR v78.7.1 when I enable WR. It's difficult to detect in a clean profile, though. If you added a few, say 50, bookmarks, then it'd be easier to detect it when you open the Bookmarks submenu. Something has changed recently to make it more pronounced even in empty profiles. I can't find said recent change, however. It's possible that is more than one and every time makes it slightly worse. Btw, I can only reproduce it on Linux.

Flags: needinfo?(dholbert)

I don't know what's happening here, no - looking frame by frame, it looks like the subview sliding in is temporarily overtaking the outer bounds for the arrow panel and causing some brief repositioning before it settles back down and resolves...

The fact that this is only reproducible with WebRender though compels me to put this in Core :: Graphics : WebRender for now.

Component: Menus → Graphics: WebRender
Flags: needinfo?(mconley)
Product: Firefox → Core

I'm clearing my needinfo since the mozregression was already given. Thanks.

Flags: needinfo?(fdiciocco)
Priority: -- → P5

Changing the priority to p1 as the bug is tracked by a release manager for the current beta.
See What Do You Triage for more information

Priority: P5 → P1
Severity: -- → S3
Flags: needinfo?(sotaro.ikeda.g)

Needinfo'ing Sotaro as owner of bug 1574746.

From later comments it sounds like this is not actually new in 87, and seems hard to reproduce.

Hi, regarding this issue, that library animation acts a bit different on other systems, its not as glitchy but it definitely slower, specially when a lot of Bookmarks are involved, I will leave a screen recording of what we see on Windows 7, 10 and Mac 11, but please note that this issue also occurs with Webrender disabled, and it also happens in Beta and Release.

Please let us know if we should log a separate issue or if its the same thing.

It seems this is an issue with OpenGL layers too. It was first introduced on 2017-07-12 (I can't get a more precise result because of missing intermediate builds), and it affected WR too. Later, the issue was fixed only on WR on 2018-01-15 (missing builds). The most recent re-intoduction of this bug in WR was in the mozregression result of comment 9.

The Basic and software WR compositors aren't affected, at least not in the current build (20210311093001).

Attached video 2021-03-11_15h27_21.mp4

Also the history -> recently closed tabs/windows submenus from the toolbar library are affected, they are not opening and closing smooth. The same submenus but from the hamburger menu are not affected. Tested with latest Nightly 88.0a1, new profile, without webrender enabled. Cannot reproduce it in Beta 87 or Release 86.

Marking as P2. Per experience review we agreed to mark as P1 bugs only bugs that will block MR1.

Priority: P1 → P2
Whiteboard: [proton-hamburger-menu]
Blocks: 1688173

This is still present on today's nightly. A friendly note, this is easier to reproduce with a lot of bookmarks.

The drop-down menus of the site information, the protections and the extensions in the overflow menu are also affected.

Whiteboard: [proton-hamburger-menu] → [proton-hamburger-menu][priority:2a]
Whiteboard: [proton-hamburger-menu][priority:2a] → [proton-hamburger-menu] [priority:2a]
OS: Linux → All
Blocks: gfx-triage

We've lived with this for a while. Maybe Sotaro can find something when he has a chance. Not a blocker as far as the graphics team is concerned.

No longer blocks: gfx-triage
Priority: P2 → P3
Component: Graphics: WebRender → Graphics

Note we don't want to confuse this with the Swiggle popup painting issues we currently have on Nightly. If you're testing something here please be sure and detail the release and platform.

Bug 1705415 - [meta] Software WebRender popups

See Also: → sw-wr-popups
Closed: 3 years ago
Resolution: --- → DUPLICATE
Whiteboard: [proton-hamburger-menu] [priority:2a]
Flags: needinfo?(sotaro.ikeda.g)
You need to log in before you can comment on or make changes to this bug.