Closed Bug 1207134 Opened 9 years ago Closed 9 years ago

Scroll while not focused not working in KDE Plasma 5

Categories

(Core :: XUL, defect)

42 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: vbocek, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20150921004016 Steps to reproduce: In Firefox developer edition 42.0a2 ("Built from https://hg.mozilla.org/releases/mozilla-aurora/rev/9f20432c24bc "). * Open firefox on Linux in KDE plasma 5 (tested on Kubuntu 15.04 live cd and Debian testing) * Open another smaller window of any app on top of firefox. * Move mouse on top of unfocused firefox window * Scroll OR * Open firefox on Linux in KDE plasma 5 (tested on Kubuntu 15.04 live cd and Debian testing) * Open another app, let's say kwrite. * Click kwrite on bottom task panel. Kwrite is now focused. * Click firefox on bottom task panel. Firefox is now focused. * Put your mouse over firefox and scroll It works as expected on Firefox 40.0.2 or in Unity (tested on Ubuntu 15.04 live cd). Actual results: Firefox does not scroll the webpage. Expected results: Firefox should scroll the webpage.
Small amendment: in the second test case, you have to click kwrite again so it minimizes. This is the correct test case: * Open firefox on Linux in KDE plasma 5 (tested on Kubuntu 15.04 live cd and Debian testing) * Open another app, let's say kwrite. * Click kwrite on bottom task panel, so that kwrite is focused. * Click kwrite on bottom task panel again. Kwrite is now minimized and firefox is now focused. * Put your mouse over firefox and scroll
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Flags: needinfo?(vbocek)
Component: Untriaged → XUL
Product: Firefox → Core
I will close this issue due to the lack of response from the reporter. If this issue persists please reopen and provide more info.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(vbocek)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.