24178 2013-12-29 23:57:40 +0000 [Custom]: No way to differentiate attribute namespaces in attributeChanged callback 2015-07-06 08:05:11 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED MOVED http://www.w3.org/TR/custom-elements/#types-of-callbacks P2 normal --- 14968 1 pdr dominicc annevk bugs dglazkov jackalmage mike pdr public-webapps public-webapps-bugzilla oldest_to_newest 97885 0 pdr 2013-12-29 23:57:40 +0000 Some valid html attributes have namespaces: http://www.w3.org/html/wg/drafts/html/master/single-page.html#attributes-0 Because the attributeChanged callback does not specify the attribute's namespace, it's not possible to differentiate the following: xuse.setAttributeNS('http://www.w3.org/1999/xlink', 'href', 'foo') or xuse.setAttribute('xlink:href', 'foo') and xuse.setAttribute('href', 'foo') One way to fix this may be to just add an optional 4th argument to the attributeChanged callback for the namespace if it is not html. 97886 1 cam 2013-12-30 01:38:06 +0000 (In reply to Philip Rogers from comment #0) > One way to fix this may be to just add an optional 4th argument to the > attributeChanged callback for the namespace if it is not html. If it's not null; xuse.setAttribute("href", "foo") sets the "href" attribute in the null namespace. 97974 2 jackalmage 2014-01-03 19:38:21 +0000 Note that SVG is dropping all of its extra namespaces in SVG2, so we can likely just ignore this. 98670 3 dglazkov 2014-01-17 00:17:28 +0000 (In reply to Tab Atkins Jr. from comment #2) > Note that SVG is dropping all of its extra namespaces in SVG2, so we can > likely just ignore this. I would <3 that. Philip? 98671 4 pdr 2014-01-17 00:24:41 +0000 (In reply to Dimitri Glazkov from comment #3) > (In reply to Tab Atkins Jr. from comment #2) > > Note that SVG is dropping all of its extra namespaces in SVG2, so we can > > likely just ignore this. > > I would <3 that. Philip? I would <3 that too. I've suggested this to the SVG2 WG at http://lists.w3.org/Archives/Public/www-svg/2014Jan/0018.html 100132 5 annevk 2014-02-10 11:30:01 +0000 Should this callback not be aligned with mutation observers? We decided to allow for namespaces explicitly there. 100180 6 dglazkov 2014-02-10 17:40:57 +0000 (In reply to Anne from comment #5) > Should this callback not be aligned with mutation observers? We decided to > allow for namespaces explicitly there. I guess this depends on whether we want to keep truly namespaced attributes in HTML, or deprecate them. 100191 7 annevk 2014-02-10 19:31:58 +0000 Well, unless we are removing setAttributeNS(), we'll have to deal somehow. But I guess I could see us not supporting that for custom elements. 105491 8 dglazkov 2014-05-08 21:48:01 +0000 (In reply to Anne from comment #7) > Well, unless we are removing setAttributeNS(), we'll have to deal somehow. > But I guess I could see us not supporting that for custom elements. Here's one idea: https://github.com/dglazkov/webcomponents/pull/2 WDYT? 105699 9 annevk 2014-05-12 09:22:41 +0000 It's close, but you actually want to queue for attribute's local name and namespace, not it's name and namespace. That would align with what we do for mutation observers and is the actual data you need to deal with namespaced attributes properly. 105738 10 dglazkov 2014-05-12 18:26:00 +0000 (In reply to Anne from comment #9) > It's close, but you actually want to queue for attribute's local name and > namespace, not it's name and namespace. That would align with what we do for > mutation observers and is the actual data you need to deal with namespaced > attributes properly. https://github.com/w3c/webcomponents/pull/13 ? 116786 11 annevk 2015-01-05 10:59:28 +0000 Seems this was fixed, no? 121643 12 hayato 2015-07-06 08:05:11 +0000 Moved to https://github.com/w3c/webcomponents/issues/168