1881903 - On Manjaro Wayland screenX and screenY property are not working properly

Status: RESOLVED WONTFIX

(Core :: Widget: Gtk, defect)

Description

[Jeremy Wang]

Attachment: Screenshot_20240224_192615.png

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

Steps to reproduce:

First, make Firefox run under Wayland Protocol by setting MOZ_ENABLE_WAYLAND=1 as an environment variable (you might need to reboot your machine to make this work).

Second, test screenX and screenY property by opening https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/screenX and run the demo. I saw that even if the mouse it really closed to the border of the screen. It still shows that the screenX is near 400 (different on each machine).

Actual results:

When I move the demo window to let its left border to collapse to the left border of the screen, and move my mouse to the left border of the demo, the screenX that it shows is near 400.

Expected results:

When I move the demo window to let its left border to collapse to the left border of the screen, and move my mouse to the left border of the demo, the screenX that it shows should be 0.

Comment 1

[Jeremy Wang]

Attachment: Screenshot_20240224_193327.png

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

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.

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Yes, this is expected. Wayland doesn't have info about general window placement. You can get mouse coordinates related to window origin only.