Summary: | Kill isSameNode on Node | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ojan Vafai <ojan> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | ahmad.saleem792, annevk, ap, bfulgham, cdumez, rniwa, syoichi |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Ojan Vafai
2012-01-03 18:32:44 PST
As mentioned in the Gecko bug, there is quite a number of uses found by code search. And there is already a report of site brokenness. It's clear that this method causes confusion, but it's quite harmless (minor performance degradation when compared to using ===). Firefox added it back here - https://bugzilla.mozilla.org/show_bug.cgi?id=1256299 We have WPT coverage as well - https://wpt.fyi/results/dom/nodes/Node-isSameNode.html?label=master&label=experimental&aligned&view=subtest&q=issamenode I think this bug can be marked as "RESOLVED INVALID" or "RESOLVED WONTFIX". Thanks! |