Bug 1774014

Summary: Dropdowns in firefox do not work on 2nd and 3rd display
Product: [Fedora] Fedora Reporter: Stephan Eicher <stephan.eicher>
Component: firefoxAssignee: Jan Horak <jhorak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: 0xalen+redhat, anto.trande, gecko-bugs-nobody, jhorak, john.j5live, kengert, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-20 14:54:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1054334    

Description Stephan Eicher 2019-11-19 12:47:32 UTC
Description of problem:
After updating my system yesterday evening (to firefox-70.0.1-4.fc31.x86_64 and some other libs) i can no longer open dropdowns (like https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select) if the firefox window is on one of the external displays of my Lenovo P50.

Dropdowns work as they should if firefox is opened on the notebook display.


Version-Release number of selected component (if applicable):
firefox-70.0.1-4.fc31.x86_64

How reproducible:
always on my maschine.

Steps to Reproduce:
1. Open firefox
2. move it to 2nd or 3rd display
3. Click on dropdown element.

Actual results:
The dropdown does not open but it is showing the click "animation".

Expected results:
The dropdown opens.

Additional info:
Lenovo P50 - was updating to latest packets like 13 hours ago. System was working before that update as it should.

Comment 1 Martin Stransky 2019-11-19 12:49:27 UTC
Jan, can you look at it please?
Thanks.

Comment 2 Jan Horak 2019-11-20 14:54:55 UTC

*** This bug has been marked as a duplicate of bug 1773715 ***