Primary eng (and PM) emails
Summary
Motivation
They were added in https://bugs.webkit.org/show_bug.cgi?id=23943 to "map points through possibly-transformed elements." At least the uses of them in LayoutTests can be replaced with getBoundingClientRect(), which also take transforms into consideration. The same is likely true of usage in the wild, too.
These two functions are also the only APIs that depend on WebKitPoint, paving the way for its eventual removal.
Compatibility Risk
The worst-case scenario is catastrophic failure of a WebKit-only site. Given the usage, actual risk seems very low indeed.
Alternative implementation suggestion for web developers
Use element.getBoundingClientRect().left/top to get the offsets that these functions would add/remove.
For example, webkitConvertPointFromNodeToPage(element, new WebKitPoint(0,0)).x can be replaced by element.getBoundingClientRect().left.
Usage information from UseCounter
webkitConvertPointFromPageToNode() ~0.0001%:Entry on chromestatus.com, crbug.com, or MDN
None.
Requesting approval to remove too?
Yes. Usage is negligible.Lgtm2
if (typeof(WebKitPoint) != "undefined")
{
// webkit code
var pnt = new WebKitPoint();
...
pnt = window.webkitConvertPointFromPageToNode(layer, pnt);
}
else
{
// non webkit code
// ...
}
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.