- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Mar 2014 08:10:58 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25016 --- Comment #2 from Philip Jägenstedt <philipj@opera.com> --- Here are all the interesting counters: Element.getAttributeNode: http://www.chromestatus.com/metrics/feature/timeline/popularity/107 Element.getAttributeNodeNS: http://www.chromestatus.com/metrics/feature/timeline/popularity/110 Element.setAttributeNode: http://www.chromestatus.com/metrics/feature/timeline/popularity/108 Element.removeAttributeNode: http://www.chromestatus.com/metrics/feature/timeline/popularity/109 Document.createAttribute: http://www.chromestatus.com/metrics/feature/timeline/popularity/111 Document.createAttributeNS: http://www.chromestatus.com/metrics/feature/timeline/popularity/112 (already removed from Blink) setAttributeNode(), at ~0.15% is also above the threshold for removal. The only ones clearly below are getAttributeNodeNS() and removeAttributeNode(). I assume that the way things would be spec'd is to have getAttributeNode() return one of the objects in the children array and for setAttributeNode(node) to just call setAttribute(node.name, node.value)? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 18 March 2014 08:11:08 UTC