SUMMARY Firefox Wayland context menus don't properly display updates for cursor movement STEPS TO REPRODUCE 1. Open Firefox 86 beta with Webrender + Wayland 2. Right-click into a website to trigger the context menu 3. move the cursor over it OBSERVED RESULT The menu selection doesn't follow the cursor. Fortunately this seems to be a rather cosmetic issue. It's not related to Firefox' Wayland widget vsync source. EXPECTED RESULT The selection indicator should follow the cursor like on Xorg or on Sway. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.11 KDE Plasma Version: 5.21 KDE Frameworks Version: 5.79 Qt Version: 5.15.2
Does it look something like this https://bugzilla.mozilla.org/show_bug.cgi?id=1685263#c3 ?
I haven't noticed any flickering yet, though your screenshot with the entry selection getting visually "stuck" looks a lot like it. I btw. deliberatly turned off widget vsync source in Firefox via about:config to rule it out as the culprit, it seemed to be entirely the same with it on or off.
Created attachment 135759 [details] Shows menu issue difference between FF85 and FF86 I experience the same issue. It's not flickering as in FF85 or earlier anymore. In FF86 the menu is drawn stable, but it doesn't properly update when the pointer is moved over it (e.g. invert menu item under pointer). See attached video for comparison. Operating System: EndeavourOS KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-zen1-1-zen OS Type: 64-bit Graphics Platform: Wayland - Multiple screens with different scaling factors
Is a fix realistic for Plasma 5.22? This seems to be one of the last, if not the only remaining blocker issue for FF Wayland on Plasma, if I'm not mistaken. :)
Seems like an upstream issue?
Yes, Vlad worked things out with the Firefox devs and it has been fixed upstream in FF Nightly. Thanks! :) Thus closing. Btw. have you noticed that sometimes right mouse button clicks go through the Firefox window surface and instead open the context menu of the Plasma desktop? Is this an aspect of a remaining subsurface issue?
I remember investigating this issue and it was firefox providing bad input region iirc.
*** Bug 434056 has been marked as a duplicate of this bug. ***