Bug 1758130

Summary: Switching away by Alt+Tab makes Firefox think that Alt is still pushed
Product: [Fedora] Fedora Reporter: Petr Kočandrle <pkocandr>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
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: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-03 11:08:38 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:

Description Petr Kočandrle 2019-10-03 11:07:09 UTC
Description of problem:
When I switch away from Firefox to another app by Alt+Tab and then I want to scroll a displayed page without switching back, just hover on Firefox window, it does not scroll but goes in page history back and forth as if I was still holding Alt key. 

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

How reproducible:
100%

Steps to Reproduce:
1. Start Firefox while another non-fullscreen app running
2. Create some browsing history
3. Switch to the other window using Alt+Tab keys
4. Hover on Firefox window without switching there and use mouse wheel to scroll

Actual results:
Firefox going in browsing history back and forth

Expected results:
The page should scroll without any url changes

Additional info:
Running a wayland session, I haven't observed such behaviour in any other app (e.g. Chromium works fine), so I expect it is a Firefox problem.

Comment 1 Martin Stransky 2019-10-03 11:08:38 UTC
That's bug 1650051.

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