Closed Bug 1790717 Opened 3 years ago Closed 3 years ago

window.screenX doesn't work after bug 1749174

Categories

(Core :: Widget: Gtk, defect)

Product:
Core
Component:
Widget: Gtk
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox-esr91 --- unaffected
firefox-esr102 --- wontfix
firefox104 --- wontfix
firefox105 --- wontfix
firefox106 --- wontfix

People

(Reporter: gregp, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Steps to reproduce:

  1. Open devtools console
  2. Type window.screenX

Actual results:
26

Expected results:
The correct value (0, if the window is maximized, for example).

Set release status flags based on info from the regressing bug 1749174

:emilio, since you are the author of the regressor, bug 1749174, could you take a look? Also, could you set the severity field?

For more information, please visit auto_nag documentation.

status-firefox104: --- → affected
status-firefox105: --- → affected
status-firefox106: --- → affected
status-firefox-esr102: --- → affected
status-firefox-esr91: --- → unaffected
Flags: needinfo?(emilio)
Keywords: regression

This is a well known wayland limitation. There are no screen-relative coordinates on Wayland.

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(emilio)
Resolution: --- → WONTFIX

This can/will never work on Wayland - it's based on legacy assumptions of the windowing API. So the question is just if it should always return 0 (instead of the windows decorations/shadow width). But most likely this can be closed as wont-fix.

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