1412544 - Nightly "Update Now" hamburger-menu popup dialog stays on top when I switch to other applications

Status: RESOLVED WORKSFORME

(Toolkit :: Application Update, defect)

Description

[:Atoll]

While technically I probably ought to click Restart Now more often, if I'm in the midst of something and I ignore it and Command-Tab to a different application, the popup dialog remains *on top of* all other applications until I resolve it.

This is, technically, good for nightly updating, but pragmatically very unfriendly to users doing more than one thing with their computer.

I'm on OS X 10.13.1 Beta (17B45a) and have seen this in Nightly a couple days this week so far. I suspect it started a few days ago, but I'm not entirely sure.

Comment 1

[Robert Strong (they/them - no direct email)]

Doug, do you recall this issue on OS X?

Comment 2

[Alex Thayer [:alexical] (she/her)]

I've only ever seen that while I have the "Disable popup auto hide" option active in the browser toolbox. I believe the pref is "ui.popup.disable_autohide". Richard, is that pref set for you?

Comment 3

[:Atoll]

(In reply to Doug Thayer [:dthayer] from comment #2)
> I've only ever seen that while I have the "Disable popup auto hide" option
> active in the browser toolbox. I believe the pref is
> "ui.popup.disable_autohide". Richard, is that pref set for you?

It's unmodified/default, it says 'false' right now in non-bold.

Comment 4

[:Atoll]

Attachment: Video of the problem on Nightly this morning.

Nightly 2017-11-02, OS X 10.13.2 Beta (17C60c).

Comment 5

[:Atoll]

I was no longer able to reproduce this in yesterday's nightly updating this morning, but I can't say why it changed.

Comment 6

[Firefox Bug Husbandry Bot]

https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Update_affecteds

Comment 7

[Jim Mathies [:jimm]]

(In reply to Richard Soderberg  [:atoll] [:�] from comment #5)
> I was no longer able to reproduce this in yesterday's nightly updating this
> morning, but I can't say why it changed.

Someone probably fixed this. Resolving this out, if you see the issue again please reopen.