Primary eng (and PM) emails
Summary
Deprecate the HTMLImageElement.x/y IDL attributes.
Motivation
These attributes are non-standard and not interoperably implemented.
Here's a demo comparing img.x/y to some other APIs:
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3090
Compatibility Risk
Medium. Usage is just below 0.03% and this API has been around for a long time.
Alternative implementation suggestion for web developers
Use getBoundingClientRect() for document coordinates and offsetLeft/offsetTop for containing block coordinates.
Usage information from UseCounter
http://www.chromestatus.com/metrics/feature/timeline/popularity/396
http://www.chromestatus.com/metrics/feature/timeline/popularity/397
Available in M36. Highest measurement yet is 0.0242%.
Entry on chromestatus.com, crbug.com, or MDN
None.
Requesting approval to remove too?
No. Deprecate for at least one release cycle.Primary eng (and PM) emails
Summary
Deprecate the HTMLImageElement.x/y IDL attributes.
Motivation
These attributes are non-standard and not interoperably implemented.
Here's a demo comparing img.x/y to some other APIs:
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3090
This is pretty simple, but Gecko and Blink still disagree.Blink's x/y seem similar to getBoundingClientRect().left/top, except that they just return 0 if there's no renderer (try removing the initial offsetLeft access) and don't take zoom into consideration (try zooming and reloading). There may be additional quirks.