jquery/jquery — pull request #796 by orkel (2012-05-25 19:33:08+00:00)
Title: Remove webkitConvertPointFromNodeToPage

Yeah, i know, i know, you guys voted on it. But hear me out for a minute, from ticket description –

"For older versions of Safari (or older mobile safari) it seems simpler to calculate offset using window.webkitConvertPointFromNodeToPage()."

In what browsers, exactly, we have webkitConvertPointFromNodeToPage and do not have getBoundingClientRect? For desktop browsers it's simple – for Safari, support for webkitConvertPointFromNodeToPage begins from Safari 4, just like for getBoundingClientRect, Chrome always had it.

Mobile browsers? There is no way to reliable know if all mobile webkit-based browsers lists here is have webkitConvertPointFromNodeToPage and do not have getBoundingClientRect. Only way to know that, is to check lowest versions of them all –

Apple iOS 3.2

Android 2.1

Blackberry 6

Blackberry Playbook 1

Palm WebOS 1.4

Meego 1.2

Dolphin 3

Kindle Fire

And i did – they all have getBoundingClientRect, which means webkitConvertPointFromNodeToPage code path will never be chosen, which means webkitConvertPointFromNodeToPage is dead code and should be removed.

cc @mikesherov