This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This method is implemented by Gecko and WebKit (and was recently removed by Blink). We probably need to specify it, since Gecko will not remove it because of backward compat reasons.
This bug needs some more pointers.
What are the backward compat reasons? Chrome 34 just shipped without createAttributeNS and while there are some complaints on blink-dev I wouldn't assume it will be reverted back into existence.
(In reply to Philip Jägenstedt from comment #2) > What are the backward compat reasons? The stuff people reported on blink-dev. > Chrome 34 just shipped without > createAttributeNS and while there are some complaints on blink-dev I > wouldn't assume it will be reverted back into existence. Sure, but that doesn't necessarily mean that other UAs are going to drop support for this. I'm unconvinced that Gecko should, for example.
(In reply to Ehsan Akhgari [:ehsan] from comment #3) > (In reply to Philip Jägenstedt from comment #2) > > What are the backward compat reasons? > > The stuff people reported on blink-dev. > > > Chrome 34 just shipped without > > createAttributeNS and while there are some complaints on blink-dev I > > wouldn't assume it will be reverted back into existence. > > Sure, but that doesn't necessarily mean that other UAs are going to drop > support for this. I'm unconvinced that Gecko should, for example. If Chrome sticks with dropping it, I'll be happy to argue with you on the Gecko side :)
Welcome back ownerElement, createAttributeNS and setAttributeNodeNS in Blink: https://codereview.chromium.org/243333003
They are still deprecated as I understand it in Blink. The new idea is to wait for a more comprehensive removal strategy. I'm inclined to wait for that as that is what the specification is targeting too at the moment.
This is tracked by bug 25016 where we will add this back most likely.
*** This bug has been marked as a duplicate of bug 25016 ***