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

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

--- Comment #13 from Jonas Sicking <jonas@sicking.cc> ---
FWIW, at mozilla we've thought of removing this function as a performance
optimization. I.e. that the fallback code path that sites hopefully provide is
likely faster than calling the function.

I.e. we expected code like

if (a.isSameNode ? a.isSameNode(b) : a === b) {
  // a is same as b
}

or

if (!Node.prototype.isSameNode) {
  Node.prototype.isSameNode = function(other) { return this === other; };
}


I don't recall if we made that assumption based on code in the wild or not.

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

Received on Thursday, 11 December 2014 00:29:25 UTC