[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 Dmitry Alexandrov changed: What|Removed |Added CC||d...@gnui.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #25 from alekksander --- (In reply to Nate Graham from comment #24) > Mouse gestures using KDE's KHotkeys? yes. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #24 from Nate Graham --- Mouse gestures using KDE's KHotkeys? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #23 from alekksander --- (In reply to Nate Graham from comment #22) > What do you mean by "Gestures"? Touchscreen gestures? Touchpad gestures? > Mouse gestures? Which ones? sorry, my bad. meant mouse gestures. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #22 from Nate Graham --- What do you mean by "Gestures"? Touchscreen gestures? Touchpad gestures? Mouse gestures? Which ones? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 alekksander changed: What|Removed |Added CC||e...@o2.pl --- Comment #21 from alekksander --- this one also breaks gestures. with MOZ_USE_XINPUT2=0 scrollbar and gestures seem to work again for me. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #20 from Vlad Zahorodnii --- a well known* -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #19 from Vlad Zahorodnii --- (In reply to Colin Griffith from comment #17) > Now in Firefox, the first scroll event after clicking is ignored. I don't > have to make a different window active to observe this effect. You're describing a well know bug in the xi2 protocol. When an application receives a XI_Enter event, it needs to reset scroll valuators. From the user's perspective, it can be seen as the first scroll being ignored. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #18 from Nate Graham --- As far as I am aware, the MOZ_USE_XINPUT2 environment variable is only consumed by Firefox. I don't know that it affects Chrome/Chromium in any way. If it does, I'll be surprised. But regardless, what you are describing sounds a whole lot like the original bug itself (Bug 394772) that is now fixed in KWin 5.19.3. Are you sure you have KWin 5.19.3 or later? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #17 from Colin Griffith --- Ok, a bug that is present in Chrome but used to be absent from Firefox is now showing up in Firefox (and slightly worse) ever since this was implemented. It might be related, but I don't know as I can't test in any other desktop environments. In Chrome, if you are in another window and then click back onto the Chrome window, so Chrome is now definitely the active window... The first scroll event sent to Chrome is ignored. Now in Firefox, the first scroll event after clicking is ignored. I don't have to make a different window active to observe this effect. For now, I've commented out that line again. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 Don B. Cilly changed: What|Removed |Added CC||donbci...@gmail.com --- Comment #16 from Don B. Cilly --- I had it since yesterday. It was quite random. 5.19.3. I updated. Kwin was part of the update. It looks fixed. I'll report if I find it isn't. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 Harald Sitter changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #15 from Colin Griffith --- Just saw KWin update, and I uncommented that line in /etc/xdg/plasma-workspace/env/neon_moz_use_xinput.sh. Scrolling in unfocused Firefox works again :D -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #14 from Harald Sitter --- https://build.neon.kde.org/view/mgmt/job/mgmt_version_list_bionic_user/383/testReport/ 03:17:10 Version for kdenlive found '20.04.2' but expected '20.04.3'! 03:17:10 The source kdeconnect-kde appears not available in our repo! 03:17:10 Looks like this needs a map (double check this!!!): 03:17:10 'kdeconnect' => 'kdeconnect-kde', 03:17:10 Version for elisa found '20.04.2' but expected '20.04.3'! 03:17:10 Version for kcmutils found '5.71.0' but expected '5.72.0'! 03:17:10 Version for kwin found '5.19.2' but expected '5.19.3'! 03:17:10 Version for plasma-phone-components found '5.18.5' but expected '5.19.3'! 03:17:10 Version for plasma-thunderbolt found '5.19.2' but expected '5.19.3'! 03:17:10 Version for plasma-sdk found '5.19.2' but expected '5.19.3'! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #13 from Colin Griffith --- Looks like the following packages are still 5.19.2, at least on my end: kwin-common kwin-data kwin-dev kwin-wayland kwin-wayland-backend-drm kwin-x11 libkwin4-effect-builtins1 libkwineffects12 libkwinglutils12 libkwinxrenderutils12 plasma-sdk plasma-thunderbolt There are also several I don't have installed, namely all the Wayland backends and various '-dbgsym' packages. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 Harald Sitter changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #12 from Harald Sitter --- 5.19.3 rollout was incomplete. kwin-x11: Installed: (none) Candidate: 4:5.19.2-0xneon+18.04+bionic+build75 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #11 from Nate Graham --- Phew, I'm not crazy. So then one of the following is happening: - The fix is not actually in Plasma 5.19.3 - The fix is in Plasma 5.19.3 but got reverted in Neon or never made it in - The fix is in Neon's Plasma 5.19.3 but it is not working -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #10 from Riccardo Robecchi --- I tested this using Neon Unstable and I can confirm it works there. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #9 from Riccardo Robecchi --- (In reply to Nate Graham from comment #8) > I am starting to wonder if this got reverted in 5.19 or in Neon or is broken > there by something else... > > Are either of you able to test with current git master or Neon Unstable with > MOZ_USE_XINPUT2=1 set and report back? Well, this is just the right timing! I have to test a server with Proxmox so I'll spin up a VM with Neon Unstable and report back. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #8 from Nate Graham --- I am starting to wonder if this got reverted in 5.19 or in Neon or is broken there by something else... Are either of you able to test with current git master or Neon Unstable with MOZ_USE_XINPUT2=1 set and report back? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #7 from Nate Graham --- (In reply to Colin Griffith from comment #5) > To be clear, you can have Firefox and Kate open, and be typing letters in > Kate while the mouse hovers over Firefox, and scroll Firefox while Kate > still accepts all keyboard inputs from you typing? Yes. > I don't know if you might be using 'focus follows mouse' or something like > that, which might mess with the behavior being described. No. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #6 from Riccardo Robecchi --- (In reply to Colin Griffith from comment #5) > (In reply to Nate Graham from comment #4) > > What you're describing perfectly matches the symptoms of Bug 394772. It's > > like the fix is not present on your machine. I also had those exact symptoms > > before it was fixed, but now it's fixed for me. :/ > > > > Did that get reverted in the stable branch or in Neon or something? It's > > definitely fixed for me with git master. > > To be clear, you can have Firefox and Kate open, and be typing letters in > Kate while the mouse hovers over Firefox, and scroll Firefox while Kate > still accepts all keyboard inputs from you typing? > > I don't know if you might be using 'focus follows mouse' or something like > that, which might mess with the behavior being described. I just checked to make sure: settings report "click to focus". Other than that, it's as you described: you have Firefox open, but not in focus, with Kate in the foreground and in focus; while you type in Kate, you can't scroll Firefox. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #5 from Colin Griffith --- (In reply to Nate Graham from comment #4) > What you're describing perfectly matches the symptoms of Bug 394772. It's > like the fix is not present on your machine. I also had those exact symptoms > before it was fixed, but now it's fixed for me. :/ > > Did that get reverted in the stable branch or in Neon or something? It's > definitely fixed for me with git master. To be clear, you can have Firefox and Kate open, and be typing letters in Kate while the mouse hovers over Firefox, and scroll Firefox while Kate still accepts all keyboard inputs from you typing? I don't know if you might be using 'focus follows mouse' or something like that, which might mess with the behavior being described. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #4 from Nate Graham --- What you're describing perfectly matches the symptoms of Bug 394772. It's like the fix is not present on your machine. I also had those exact symptoms before it was fixed, but now it's fixed for me. :/ Did that get reverted in the stable branch or in Neon or something? It's definitely fixed for me with git master. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #3 from Riccardo Robecchi --- (In reply to Nate Graham from comment #2) > Hmm, this was supposed to be non-destructive with KWin from Plasma 5.19.3, > which added a change to fix the bugs you're seeing. :/ > > Folks who are affected: can you describe the contidions under which you're > affected? Is it always? only when using more than one monitor? When another > window is maximized? Etc. I am using a single monitor. The issue is present when: - Firefox is in the background, both maximised or not, and I have another window in the foreground (e.g. Kate); - Firefox is in the foreground, another window comes in front of it (e.g. I open Kate) and this new window is then minimised; - I switch to another window, both using alt+tab or the taskbar/Dock (I use Latte), and then switch back. In all cases I have to minimise Firefox and restore it for scrolling to come back. It has to be noted that scrolling is broken not just when it is in the background, but in the foreground as well. (In reply to Colin Griffith from comment #1) > For what it's worth, I imagine this is probably more of an issue for those > of us with more than one monitor, as it makes it more likely to have more > than one app maximized at a time. That's the most likely scenario in which > you'd want to be able to scroll a web page while the browser is not in focus. This issue is also impacting those who use side-by-side windows, with Firefox on one half of the screen and another window in the other. This is one of the most common use cases for me. I also tend to use Yakuake following instructions from a web page, which requires scroll behaviour to work. I am sure there are other use cases as well. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 --- Comment #2 from Nate Graham --- Hmm, this was supposed to be non-destructive with KWin from Plasma 5.19.3, which added a change to fix the bugs you're seeing. :/ Folks who are affected: can you describe the contidions under which you're affected? Is it always? only when using more than one monitor? When another window is maximized? Etc. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 Harald Sitter changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 424584] MOZ_USE_XINPUT2=1, exported by neon-settings, breaks Firefox scroll behaviour
https://bugs.kde.org/show_bug.cgi?id=424584 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com, ||vlad.zahorod...@kde.org Summary|neon-settings |MOZ_USE_XINPUT2=1, exported |0.0+p18.04+git20200713.0733 |by neon-settings, breaks |breaks Firefox scroll |Firefox scroll behaviour |behaviour | -- You are receiving this mail because: You are watching all bug changes.
