As I understand it, webkitConvertPointFromNodeToPage is a requirement for implementing WebKitPoint (bug 850805) as the two are frequently used together. As such, if we are to fix bug 850805 we should do this as well. Reference: http://developer.apple.com/library/safari/#documentation/DataManagement/Reference/DOMWindowAdditionsReference/DOMWindowAdditions/DOMWindowAdditions.html Of interest link questioning the need for webkitConvertPointFromNodeToPage: https://.com/jquery/jquery/pull/796

So is this just a conversion function from relative coordinates (e.g. within an element/node) to page coordinates? If so, I think much of the implementation that I did for caretPositionFromPoint might be able to be leveraged here.

There is now a stub docs page for this: https://developer.mozilla.org/en-US/docs/Web/API/Window.convertPointFromNodeToPage

Non-dead reference link: https://developer.apple.com/library/iad/documentation/DataManagement/Reference/DOMWindowAdditionsReference/index.html#//apple_ref/javascript/instm/DOMWindow/webkitConvertPointFromNodeToPage