Re: [w3ctag/design-reviews] ViewportAPI naming Re-review (#172)

There's a long list of interfaces I've found (searching Mozilla's WebIDL) that use X/Y naming.  The vast majority of them are for points, deltas, or things like sizes of blurs, not for rectangles.  I think window.screenX/Y and MediaTrackConstraintSet.viewportOffsetX/Y are the only examples of X/Y naming in this list that are for rectangles, which is what the new proposed naming in the Viewport API is doing.

<details><summary>Expand for full list...</summary>

* CanvasRenderingContext2D.shadowOffsetX/Y
* DOMMatrix (various parameters and methods)
* Document.createTouch() parameters
* DragEvent.initDragEvent() parameters
* MediaTrackConstraintSet.viewportOffsetX/Y (which goes along with viewportWidth/Height), and the same for MediaTrackSupportedConstraints
* various properties on MouseEvent and UIEvent
* parameters to MouseEvent.initMouseEvent() and MouseScrollEvent:initMouseScrollEvent()
* PannerOptions.positionX/Y/Z and orientationX/Y/Z, and same on PannerNode
* PointerEvent.tiltX/Y
* a pile of things in SVG that I don't want to list all of
* various properties on Touch
* parameters to WebKitCSSMatrix
* WheelEvent.deltaX/Y
* window.screenX/Y, scrollX/Y, pageX/YOffset

</details>

-----

There's a slightly larger amount of Left/Top naming for rectangles (although much less in general):  Element.scrollTop/Left, Element.clientTop/Left, HTMLElement.offsetTop/Left, Screen.availTop/Left.  All of the Left/Top naming in the platform that I found (searching Mozilla's WebIDL) appears to be for positions of rectangles.

So I still think I somewhat prefer Left/Top naming, but if others disagree I guess I'm not in a position to insist.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/172#issuecomment-298153171