Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[cssom-view] Window#screenLeft/screenTop #1091

Closed
foolip opened this issue Mar 9, 2017 · 4 comments
Closed

[cssom-view] Window#screenLeft/screenTop #1091

foolip opened this issue Mar 9, 2017 · 4 comments

Comments

@foolip
Copy link
Member

foolip commented Mar 9, 2017

https://drafts.csswg.org/cssom-view/#extensions-to-the-window-interface

screenX and screenY are in the spec, but not screenLeft or screenTop.

These two attributes are in Chromium, EdgeHTML and WebKit, but not Gecko, as tested with:
https://software.hixie.ch/utilities/js/live-dom-viewer/saved/4927

Use counters:
https://www.chromestatus.com/metrics/feature/timeline/popularity/697
https://www.chromestatus.com/metrics/feature/timeline/popularity/698

Risk of removal is hard to judge, but given three implementations standardization should be the default choice.

In Chromium and WebKit, they are simply aliases of screenX and screenY:
https://chromium.googlesource.com/chromium/src/+/706a26bfd8ee3677c8b59fc1a6859276ab7686c7/third_party/WebKit/Source/core/frame/LocalDOMWindow.h#139
https://trac.webkit.org/browser/trunk/Source/WebCore/page/DOMWindow.h?rev=211654#L170

@zcorpan

@zcorpan zcorpan self-assigned this Mar 9, 2017
csnardi added a commit to csnardi/csswg-drafts that referenced this issue May 11, 2018
Given that usage of these attributes are high and that they are implemented in Chrome, WebKit, and Edge, standardization seems like the best option for screenLeft and screenTop. Add them into the spec as simple aliases of screenX and screenY.

Fixes w3c#1091.
@foolip
Copy link
Member Author

foolip commented Oct 13, 2018

https://bugs.chromium.org/p/chromium/issues/detail?id=695572 had been closed as WontFix, i.e., this won't be removed from Chromium because the usage is too high. @tabatkins, can you send a spec change for this, or find someone who can?

@foolip
Copy link
Member Author

foolip commented Oct 13, 2018

(It is still the case that this is missing in Gecko only. @emilio may be interested to know this.)

@emilio
Copy link
Collaborator

emilio commented Oct 13, 2018

Thanks for the heads-up :)

@emilio
Copy link
Collaborator

emilio commented Oct 13, 2018

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1498860 to keep track of this.

Looks like there's a spec change ready in #2669, just no editor for the spec... :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants