1735712 - Clicking "About Firefox" causes screen to flash as window appears in 2 different places.

Status: RESOLVED DUPLICATE of bug 1738056

(Core :: Widget: Cocoa, defect, P2)

Description

[MarjaE]

Attachment: Screen Recording 2021-10-14 at 1.43.46 AM.mov

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:93.0) Gecko/20100101 Firefox/93.0

Steps to reproduce:

Clicked "About Firefox"

Actual results:

The screen flashed as the window loaded in the upper-lft corner of the screen, and flashed again a split-second later as it loaded in the middle.

Expected results:

It should load once, not twice.

Comment 1

[MarjaE]

Same behavior in troubleshoot mode.

Comment 2

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

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

Comment 3

[Stephen A Pohl [:spohl]]

I'm going to move this to accessibility to give it more visibility. The fix will most likely be under Widget::Cocoa though.

Comment 4

[Morgan Reschenberg [:morgan]]

We should triage this to where it'll be fixed.
We use the 'access' keyword along with the '[access-sX]' whiteboard tag to track accessibility-relevant bugs that originate in other components.
Triaging as [access-s2] due to possible injury for users with vestibular disabilities.

Comment 5

[Stephen A Pohl [:spohl]]

(In reply to Morgan Reschenberg [:morgan] from comment #4)

We should triage this to where it'll be fixed.
We use the 'access' keyword along with the '[access-sX]' whiteboard tag to track accessibility-relevant bugs that originate in other components.
Triaging as [access-s2] due to possible injury for users with vestibular disabilities.

Thanks. Should I simply add the 'access' keyword when I encounter one of these bugs, and you will be adding the '[access-sX]' whiteboard tag during your own triage of bugs with the 'access' keyword?

Comment 6

[Morgan Reschenberg [:morgan]]

(In reply to Stephen A Pohl [:spohl] from comment #5)

(In reply to Morgan Reschenberg [:morgan] from comment #4)

We should triage this to where it'll be fixed.
We use the 'access' keyword along with the '[access-sX]' whiteboard tag to track accessibility-relevant bugs that originate in other components.
Triaging as [access-s2] due to possible injury for users with vestibular disabilities.

Thanks. Should I simply add the 'access' keyword when I encounter one of these bugs, and you will be adding the '[access-sX]' whiteboard tag during your own triage of bugs with the 'access' keyword?

Yep! Anything tagged with access will show up in our weekly triage rotation, and we'll add the appropriate severity whiteboard tag.
If you're interested in learning more about how/why we triage things with the severities we do, you can check out our triage page

Comment 7

[Stephen A Pohl [:spohl]]

Thanks!

Comment 9

[Markus Stange [:mstange]]

Is this a regression?

Comment 10

[Mehmet]

I see this for a very long time (over a lot of FF Stable Releases now.)

Comment 11

[Mehmet]

Hi Markus,

I did a manual bisect and found the regression range:

Good Build: 2021-08-03-22-01-19-mozilla-central/

Bad Build: 2021-08-04-09-39-31-mozilla-central/

I hope this helps you to find the culprit change.

Thanks :)

Comment 12

[Markus Stange [:mstange]]

Thanks! I was still able to reproduce it in your good build, so I used mozregression to find a new regression range, and it led me to bug 1660392. And it turns out this bug is already tracked as a regression from that, in bug 1738056.

Comment 13

[Mehmet]

Thanks for your follow up and finding the report that is already tracking the regression.