Open Bug 1421578 Opened 7 years ago Updated 2 years ago

menus failed after wake up from sleep with dual screen

Categories

(Firefox :: Menus, defect, P5)

57 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: rlcor102008, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171112125346

Steps to reproduce:

Background info: 
- using a notebook with the desktop extended to an external monitor
- using Firefox in safe mode
- Windows 10

Steps to reproduce:
- Open firefox, maybe open a few tabs of different sites
- Leave the notebook timeout to sleep. Make sure Windows shuts the screen panel completely (and not just showing a screen saver)
- Press and few key to bring Windows out of sleep



Actual results:

Clicking any menu buttons no long works. You can still switch to different tabs but no menu works.  This includes the menu button, the dropdown menus on top of the window (if any), right click context menus


Expected results:

Menu should work
I should add that if there is no external monitor attached, it seems to work fine. I don't know if it is related to display driver issues.  Other browsers work fine.
Component: Untriaged → Menus
The need for a very specific OS and hardware arrangement, as well as needing to wait for the device to suspend/sleep means that investigating this will unfortunately be very time consuming. As you can reproduce this problem, it would be a huge if you were able to help narrow down when this broke. The mozregression[1] tool lets you input known good/bad dates and guides you through pinpointing exactly which changeset broke some behavior. Failing that, even confirming if this problem existed prior to 57 would be useful.  

1. http://mozilla.github.io/mozregression/
Flags: needinfo?(rlcor102008)
Priority: -- → P5
I have run the mozregression tool and here is the result
Flags: needinfo?(rlcor102008)
Do you need more info?
Was experiencing a similar issue, on a windows 7 desktop. Same behavior would happen after Windows went to sleep. New since 57, still occurred on 58. Just found a potential workaround this morning, checking the box to revent accessibility services from accessing your browser seems to stop the problem, at least so far
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: