Open Bug 1772164 Opened 2 years ago Updated 2 years ago

No hover events and sometimes position of cursor has an offset of where Firefox thinks it is and where it actually is

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 101
defect

Tracking

()

UNCONFIRMED

People

(Reporter: willduncannn, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0

Steps to reproduce:

The bug occurs frequently, but I cannot determine the exact cause.
To trigger the bug open tabs, open webpages, switch tabs, close tabs. Also using shortcuts like Ctrl+T and Ctrl+W

Actual results:

Sometimes hover events seem to be disabled (not only in the webview, but the entire window, including the _ [] X indicators in the title bar). Hover events work in extension popups and the Firefox menu. When this happens, you can place the mouse over an element and click it and it will work. The cursor will change depending on the clicked element (as if you hovered it) and will stay like that until you click something else that would show a different hover cursor.

Additionally, sometimes I also stop being able to click anything. I cannot drag the window, click on tabs, open the menu, etc. If I move the mouse several centimetres above the target, then sometimes it triggers a hover event and I can click it. It catches clicks and keeps Firefox in focus even though the click was technically outside of the application.

I did not experience this bug on the previous version (100).
Firefox: 101.0 64-bit snap for Ubuntu canonical-002 - 0.1
Ubuntu 22.04 LTS x86_64
Gnome 42.0 (Wayland)
5.15.0-33-generic
11th Gen Intel i7-1165G7 (8) @ 4.700GHz
Intel TigerLake-LP GT2 [Iris Xe Graphics]

Expected results:

Hover events should be triggered properly and clicks should register at the actual position of the mouse pointer.

The only fix I have found is to restart the browser. After a restart, for a while, everything functions correctly.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Hi,

same here, Firefox 101 Archlinux Gnome Wayland

when it happens, I also cannot resize/maximize the window, which seems completely stuck after resize.

Julien

It seems this bug can happen without any user input. No opening, closing, etc. of tabs needed. Simply leaving Firefox in the background for a few minutes also causes this bug to appear.

Opening a new window fixes the problem for the new window. Sending a tab to a new window also restores the normal behavior for some time

It might have something related to multiple monitor: this morning, I hadn't the problem for 3 hours, then I switch my second monitor on, and then the problem appeared short time after

Flags: needinfo?(willduncannn)
Flags: needinfo?(julien)
Blocks: wayland
Priority: -- → P3

I will try to record a screencast of the issue in the coming days.
I have switched to using Firefox 100 with the deb PPA repository and this issue does not occur on this installation. For the recording, I will install again version 101 via snap.
I can confirm what @julien said: by opening a new window (even while having one "bugged" already opened), the new window works correctly. Dragging tabs from the bugged window to the working one (or to their own one) makes them work correctly again.
I am also using a second monitor.

Hi,
I still don't know what triggers the bug, but it also happens in a single monitor setup.
Will try to record when I get an idea of the cause

Flags: needinfo?(julien)

Seems enabling "full" wayland support (MOZ_ENABLE_WAYLAND=1) as mentioned in #1774531 fixes this issue

You need to log in before you can comment on or make changes to this bug.