1490327 - [Mac] Artifacts are displayed while shrinking the meatball and chevron menus.

Status: NEW

(DevTools :: General, defect, P3)

Description

[Emil Ghitta, QA [:emilghitta]]

[Affected versions]:
64.0a1 (BuildId:20180910220142)
63.0b5 (BuildId:20180910132416)

[Unaffected versions]: 
62.0 (BuildId:20180830143136)
60.2.0esr (BuildId:20180903060751)

[Affected platforms]:
macOS 10.13.6

[Steps to reproduce]:
1. Launch Firefox.
2. Open the developer tools.
3. Open the "meatball" menu and minimize the Developer tools by using the "CTRL" + "-" keyboard combination (while the meatball menu is open).

[Expected result]:
The menu is resized without issues or the "CTRL" + "-" keyboard combination is not functional while the meatball or chevron menu is open.

[Actual result]:
Artifacts are displayed while the meatball or chevron menu is shrinked.

[Regression range]:
This seems to be a regression.

Mozregression points out Bug 1461522 for causing this regression.

Last good revision: ea72ff9a6e23abf3aa52aaaf06a9ba8b18ca39c7
First bad revision: cc6ec2789c9d50a686f4df5a70bf0f1173d1d32e

Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ea72ff9a6e23abf3aa52aaaf06a9ba8b18ca39c7&tochange=cc6ec2789c9d50a686f4df5a70bf0f1173d1d32e

[Note]
For further information regarding this issue please observe the following screencast: https://drive.google.com/open?id=1NbxDI9RDX3_JlI7qp5P35WbcKegqfaZF

Comment 1

[Emil Ghitta, QA [:emilghitta]]

(In reply to Emil Ghitta, QA [:emilghitta] from comment #0)
> 3. Open the "meatball" menu and minimize the Developer tools by using the
> "CTRL" + "-" keyboard combination (while the meatball menu is open).
> 
> [Expected result]:
> The menu is resized without issues or the "CTRL" + "-" keyboard combination

It should be "Command" instead of "CTRL"..my bad.

Comment 2

[Brian Birtles (:birtles)]

It sounds like the simplest thing here would be to just close the menu whenever we're zooming.

Comment 3

[Liz Henry (:lizzard)]

Marking fix-optional for 64. We could still take a patch for 65, and if it's verified and doesn't seem risky, could still take fixes for 64 as well.

Comment 4

[Pascal Chevrel (relman team) -> :pascalc]

Updating tracking flags as we get closer to the 64 release.

Comment 5

[Liz Henry (:lizzard)]

Marking fix-optional for 65 and 66 so that these already triaged issues don't show up repeatedly in weekly regression triage. Happy to take a patch in nightly.