[Bug 27424] Node.isSameNode() has non-trivial usage

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27424

--- Comment #15 from Ryosuke Niwa <rniwa@webkit.org> ---
(In reply to Philip Jägenstedt from comment #14)
> Ryosuke, do you have anything to say on the prospects of removing
> isSameNode() in WebKit?

I don't have a strong opinion either way, and I haven't talked with my
colleagues yet but my gut feeling is that we're not gonna remove this function;
at least that's what I'm going to advocate if anyone suggests to remove this
function in WebKit.

As far as I've searched through GitHub [1], most of code samples I found that
uses isSameNode are WebKit/Blink tests. This contradicts the claim that
removing isSameNode is a meaningful performance optimization or that many Web
authors rely on this function instead of ===.

I can be convinced otherwise with a presence of more data indicating having
this function is more harmful than worth the potential compatibility benefit.

[1]
https://github.com/search?l=javascript&p=80&q=isSameNode%28&ref=searchresults&type=Code&utf8=✓

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 17 December 2014 14:13:10 UTC