[Bug 27344] Remove Element.setAttributeNodeNS()?

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

--- Comment #21 from Philip Jägenstedt <philipj@opera.com> ---
(In reply to Olli Pettay from comment #20)
> (In reply to Philip Jägenstedt from comment #19)
> > There was an attempt to remove setAttributeNodeNS that was reverted
> Why was is reverted?

It was reverted in https://codereview.chromium.org/243333003 together with
Document.createAttributeNS() and Attr.ownerElement. I don't know which API
caused the most breakage, but Attr.ownerElement has the highest usage of them:
https://www.chromestatus.com/metrics/feature/timeline/popularity/160

Document.createAttributeNS() is close to zero and has been from the start:
https://www.chromestatus.com/metrics/feature/timeline/popularity/112

> > If Gecko were to remove setAttributeNodeNS(), would you also change
> > setAttributeNode() to be like the current setAttributeNodeNS()? Using the
> > qualified name seems Web compatible, because Blink/WebKit do that.
> Do we have data about setAttributeNode usage for blink?
> (We don't have for Gecko)

We do:
https://www.chromestatus.com/metrics/feature/timeline/popularity/108

The relatively high usage is why I guess nobody can be exciting about changing
setAttributeNode(), but setAttributeNode() doesn't work the same with
namespaces in Gecko and Blink, the difference likely doesn't matter for Web
compat.

At this point, I think only options 1 and 3 in comment #9 make sense. Option 1
is likely less risky. Do you have a preferred course of action?

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

Received on Thursday, 20 November 2014 09:54:13 UTC