Bug 424914 - Can't click on the topmost pixel of firefox tabs
Summary: Can't click on the topmost pixel of firefox tabs
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL: https://bugzilla.mozilla.org/show_bug...
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-02 10:36 UTC by Mark Smith
Modified: 2020-10-24 16:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Clicking when the mouse is at the top like that does nothing. (6.46 KB, image/png)
2020-08-02 10:36 UTC, Mark Smith
Details
Video of the issue on a brand new firefox profile. (1.63 MB, video/mp4)
2020-08-09 16:54 UTC, Mark Smith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Smith 2020-08-02 10:36:39 UTC
Created attachment 130572 [details]
Clicking when the mouse is at the top like that does nothing.

SUMMARY
    I have a strange problem with Firefox today, which I think happened after the latest batch of updates for KDE Neon (user edition), out of nowhere I can no longer change tabs by ramming the mouse at the very top of the screen (Firefox is maximized) and clicking. I have to move a few pixels down or my click is ignored.

See screenshot, if I do that, I can't click on tabs. Even though the popup appears for said tab. This is not related to Firefox because it also happens in GNU Icecat out of nowhere after the latest batch of updates. 

STEPS TO REPRODUCE
1. Move mouse to the topmost part of the screen with Firefox maximized
2. Click to different tabs

OBSERVED RESULT
99% of the time, click is ignored

EXPECTED RESULT
Click should activate the tab I have under the mouse. 

SOFTWARE/OS VERSIONS
OS: KDE neon 5.19
Kernel: x86_64 Linux 5.3.0-51-generic
Uptime: 14m
Packages: 2157
Shell: bash 4.4.20
Resolution: 1680x1050
DE: KDE 5.72.0 / Plasma 5.19.4
WM: KWin
GTK Theme: Breeze-Dark [GTK2/3]
Icon Theme: breeze-dark
CPU: Intel Core i5-3570K @ 4x 3.8GHz [40.0°C]
GPU: GeForce GTX 1060 6GB
RAM: 1864MiB / 7915MiB


ADDITIONAL INFORMATION
It's not related to Firefox, that's for sure, because it happens in some ancient IceCat build I downloaded ages ago as well.
Anyway, this issue makes Firefox totally unusable for me, and I will unfortunately have to switch to Windows until it's fixed.
Comment 1 Mark Smith 2020-08-02 10:38:18 UTC
Also happens on a brand new user created just to test this.
Comment 2 Derek Christ 2020-08-03 07:03:37 UTC
As far as I know problems like this can arise when using different GTK themes or scaling options that make the close buttons on the upper right corner bigger than the height of the tabs. Since you are using Breeze as GTK theme, I am not sure why there is a 1 pixel gap in your case.
Could you go to the customize window in Firefox and try different density options at the bottom? (if its set to compact by any chance, switching to normal could fix the problem)

If nothing helps, editing the user-chrome.css of Firefox is always an option, but this is the last thing to try in my opinion.

Indeed Firefox client side decorations integration could be better (I have a similar issue with the close button)
Comment 3 Mark Smith 2020-08-03 12:28:56 UTC
I tried messing with density, themes, removing the close button, restoring the default theme, also like I said I used a new user profile so that everything would be default but it still happens. It's caused by one of the latest updates to KDE Neon because I've been using it for years and I never had this problem before.
Comment 4 Mark Smith 2020-08-03 12:29:27 UTC
Oh and by the way, it seems that it works sometimes, I would say the probability of the click registering is like one click out of 10. Anyone else having this problem?
Comment 5 Mark Smith 2020-08-09 12:00:25 UTC
I just tested this behavior on a freshly booted live iso of KDE Neon and the same thing happens. So I can't be the only one with this issue.
Comment 6 Mark Smith 2020-08-09 16:54:58 UTC
Created attachment 130737 [details]
Video of the issue on a brand new firefox profile.

Video of the issue on a brand new firefox profile.
Comment 7 Nate Graham 2020-08-10 19:19:42 UTC
Are you using screen scaling of any type? And are you using the X11 session of the Wayland session? (if you don't know, it's X11)
Comment 8 Mark Smith 2020-08-11 13:19:23 UTC
X11 and no scaling. Consider the fact it also happens on a fresh boot of the latest iso of KDE Neon.
Comment 9 Nate Graham 2020-08-11 20:51:01 UTC
Thanks for the info! A few more questions:

1. What does get clicked on? Nothing? The desktop? The window below it?

2. Do you have a top screen edge set in System Settings > Workspace Behavior > Screen Edges?
Comment 10 Nate Graham 2020-08-21 17:03:50 UTC
This turns out to be an issue in Firefox itself: https://bugzilla.mozilla.org/show_bug.cgi?id=1660212
Comment 11 Mark Smith 2020-09-12 08:48:57 UTC
Dear Nate, sorry for not replying but eventually even though my user experience was miserable to the point I eventually switched to ungoogled chromium, I was forced to switch back to Windows because the 20.04 updated killed grub on my Neon install, that's why I didn't reply. Anyway I understand that it's caused by firefox (even though I don't really understand the reason or if there is any workaround. It seems strange that so few people noticed this insanely annoying issue. If anyone figures out a workaround so that I can use Firefox without the titlebar and without feeling miserable and pathetic due to missing clicks (ok I'm exagerating, it's not that bad but it's still not good either) I would be really grateful.

Btw it doesn't happen on the Linux Mint I'm using on my ancient laptop.
Comment 12 Mark Smith 2020-10-24 10:09:36 UTC
I discovered the variable that causes that weird behavior was set by this scripts
 /etc/xdg/plasma-workspace/env/neon_moz_use_xinput.sh
This is a default script from Neon, it was still there when I reinstalled. 

I think this script must be removed because it causes that issue until you delete it manually. Obviously it happens also in the live iso if you want to test it.
Comment 13 Nate Graham 2020-10-24 16:12:14 UTC
Neon could fix this for users by configuring firefox to use server-side decorations by default instead of client-side decorations, which are affected the the "dead row of pixels" bug. Server-side decorations are not affected in this way.