This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25370 - AttrExodus: Specify document.createAttributeNS
Summary: AttrExodus: Specify document.createAttributeNS
Status: RESOLVED DUPLICATE of bug 25016
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-16 18:48 UTC by Ehsan Akhgari [:ehsan]
Modified: 2014-08-18 14:20 UTC (History)
4 users (show)

See Also:


Attachments

Description Ehsan Akhgari [:ehsan] 2014-04-16 18:48:30 UTC
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.
Comment 1 Anne 2014-04-16 19:24:24 UTC
This bug needs some more pointers.
Comment 2 Philip Jägenstedt 2014-04-17 22:21:24 UTC
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.
Comment 3 Ehsan Akhgari [:ehsan] 2014-04-18 02:17:59 UTC
(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.
Comment 4 Ms2ger 2014-04-18 07:21:39 UTC
(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 :)
Comment 5 Philip Jägenstedt 2014-04-22 21:05:30 UTC
Welcome back ownerElement, createAttributeNS and setAttributeNodeNS in Blink:
https://codereview.chromium.org/243333003
Comment 6 Anne 2014-04-23 10:33:47 UTC
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.
Comment 7 Anne 2014-08-18 14:20:17 UTC
This is tracked by bug 25016 where we will add this back most likely.
Comment 8 Anne 2014-08-18 14:20:30 UTC

*** This bug has been marked as a duplicate of bug 25016 ***