Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多
Solved 封存

mouse not responsive at right window edge (linux wayland)

ibrahimasif1234 replied
ibrahimasif1234

Greetings!

I am using the firefox enterprise version and I have noticed an issue that the browser does not capture mouse events when the pointer is at rightmost edge of the firefox window. For example, on this website near the edge the pointer would initially focus on the scroll bar and then lose focus at the edge (see attached images).

This issue does not persist on x11, and only seems to exist on wayland. It also exists on other flavours of firefox on wayland.

If more information is required, feel free to send me a ping.

Greetings! I am using the firefox enterprise version and I have noticed an issue that the browser does not capture mouse events when the pointer is at rightmost edge of the firefox window. For example, on this website near the edge the pointer would initially focus on the scroll bar and then lose focus at the edge (see attached images). This issue does not persist on x11, and only seems to exist on wayland. It also exists on other flavours of firefox on wayland. If more information is required, feel free to send me a ping.
附加的畫面擷圖
從原來的回覆中察看解決方案

選擇的解決方法

It seems to have been fixed.

Thanks to everyone for the support!

所有回覆 (4)

I’ve seen the same behavior on Wayland with Firefox Enterprise. The pointer seems to ‘skip’ the very edge, especially near scrollbars. Switching to X11 fixes it for me, so it seems Wayland-specific.

When you say "enterprise" do you mean the Firefox ESR?

This sounds like a bug that should be opened here:

https://bugzilla.mozilla.org/home

> This issue does not persist on x11, and only seems to exist on wayland. It also exists on other flavours of firefox on wayland.

The described behaviour exists on wayland only, on all flavours of firefox (including ESR).

I will create a bug report.

選擇的解決方法

It seems to have been fixed.

Thanks to everyone for the support!