- From: <bugzilla@jessica.w3.org>
- Date: Fri, 06 Apr 2012 21:45:08 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16563 --- Comment #7 from Jonas Sicking <jonas@sicking.cc> 2012-04-06 21:45:07 UTC --- Given how very rare namespaced attributes are, I really see very little reason to make "sugar features" like the attribute filter work with them. If someone really needs to observe a namespaced attribute they can do that by not having a filter. Making the filter work on the name rather than localName doesn't seem to help people that want to do the right thing, since then you should be observing a specific localName+namespace. To answer comment 1, the reason an implicit * namespace doesn't make sense is that there no more commonalities between attributes with a "value" localName, but different namespaces, than attributes whose name end with "er". If someone requests to only be notified about changes to the "value" attribute, they are unlikely to check that the change was to an attribute in the null namespace, and so would get tripped up by changes to an "xlink:value" attribute. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 6 April 2012 21:45:11 UTC