1697741 - [Proton] Visual glitches when accessing the FxA submenu

Status: RESOLVED WORKSFORME

(Firefox :: Menus, defect)

Description

[Brindusa Tot, Desktop QA]

Attachment: VisualIssue.mp4

Tested with:
Nightly 88.0a1 (2021-03-10)

Tested on:
Windows 10, Windows 7

Preconditions:
In about:config, set browser.proton.enabled = true

Steps:

1. Launch firefox and sign in into FxA .
2. Open the Hamburger menu
3. Go to FxA submenu.
4. Now back to hamburger menu with < button.
5. Repeat steps 3 and 4 few times.
6. Under FxA submenu hover the mouse over few options.
7. Hover the mouse over the < button.

Actual result:
Visual glitches appear on the hamburger menu and FxA submenu.

Expected result:
the hamburger menu and FxA submenu should be displayed correctly, without any visual glitch.

Note:
The issue is reproducible both with and without Proton enabled.
The issue is easy visible on Dark themes, but it is reproducible also on Default theme

Comment 1

[Alin Ilea, Desktop QA]

Attachment: 2021-03-11_10h54_11.mp4

The same glitch also occurs after reproducing the initial issue, without closing the Hamburger menu, hover the mouse cursor over the zoom buttons (- +).

Comment 2

[Itiel]

Attachment: All Tabs - Screenshot

The same in the all tabs list.

Comment 3

[Alin Ilea, Desktop QA]

Attachment: 2021-03-12_12h01_33.mp4

Also I am getting this one. Seems to be the same glitch as in the bug description but here in my case the browser is freezing, if you look at my mouse cursor, the browser doesn't respond until I click anywhere...

Comment 4

[Mike Conley (:mconley) (:⚙️)]

As this is reproducible with and without Proton enabled, I suspect this is a graphics invalidation issue. brindusat, can you help us find a regression range?

Comment 7

[Alin Ilea, Desktop QA]

This is the same issue as in the bug 1698067, which was already fixed. I just verified the issue in the latest Nightly build 88.0a1 (build id: 20210316094954) and it seems to be fixed, so I don't think a regression range is still needed here.

Comment 8

[Sotaro Ikeda [:sotaro]]

:brindusat, is the problem addressed for you with latest nightly?

Comment 9

[Brindusa Tot, Desktop QA]

Verified with latest Nightly 88.0a, build Id 20210316214855, and this issue is not reproducible any more. As Alin stated in comment 7, probably this bug was fixed with the fix for bug 1698067.

Marking this as Resolve WFM.

Comment 10

[Sotaro Ikeda [:sotaro]]

Great! Thank you.