Closed Bug 1468464 Opened 6 years ago Closed 6 years ago

[Win] Dropdowns stuck in place when button moves

Categories

(Firefox :: Menus, defect)

All
Windows
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- wontfix
firefox-esr60 --- wontfix
firefox60 --- wontfix
firefox61 --- wontfix
firefox62 --- wontfix

People

(Reporter: cfogel, Unassigned)

Details

Attachments

(1 file)

[Affected versions]:
- 60, 61.0b10, 62.0a1 (2018-06-12)

[Affected platforms]:
- Win 10x64;

[Steps to reproduce]:
1. Launch Firefox;
2. Click on the browser's restore down button(so it's not on full-screen);
3. Click on the Hamburger menu button;
4. Grab and move the browser quickly  to another location on the screen.

[Expected result]:
- The dropdown menu moves with the parent button.

[Actual result]:
- The dropdown is is stuck in place.

[Regression range]:
- was able to reproduce on v45.

[Additional notes]:
- attached screenshot with the issue;
- the fade-out part is as expected;
- reproducible for any other button/dropdown as well;
- not reproducible on MacOS(10.13.4) and Ubuntu(16.04LTS).
Correction on platform and summary.
OS: All → Windows
Summary: Dropdowns stuck in place when button movees → Dropdowns stuck in place when button moves
Reproducible on Win 7(x86) as well.
Summary: Dropdowns stuck in place when button moves → [Win] Dropdowns stuck in place when button moves
This appears to affect all popups and is not a common use case among users. As well, there is no data loss and it is easy to re-open the menu.

This happens because dragging the window removes focus from the menu and the menu closes on blur.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
I'm well aware that this is an edge case, but it does not happen on other browsers (ex: on Chrome/IE the drop-down is closed before dragging the window around). Wouldn't it be safer to reopen this and set it to the lowest priority, so we can keep track of it?
Flags: needinfo?(jaws)
I'm actually unable to reproduce this again with Firefox Nightly 63.0a1 (2018-07-09) (64-bit) on Windows. I should have marked this as WONTFIX instead of INVALID, but now that I see it has been potentially fixed I'm changing the resolution to WORKSFORME.
Flags: needinfo?(jaws)
Resolution: INVALID → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: