Remove Firefox deprecated nodeValue, getAttributeNode, specified
|Reported by:||dmethvin||Owned by:||timmywil|
Firefox 13 generates a pretty large set of warnings in our attribute unit tests:
Use of getAttributeNode() is deprecated. Use getAttribute() instead. Use of attributes' nodeValue attribute is deprecated. Use value instead. Use of document.createAttribute() is deprecated. Use element.setAttribute() instead. Use of attributes' specified attribute is deprecated. It always returns true.
The fact that
.specified is already broken may already be causing some bugs. We should either 1) remove these uses entirely or 2) feature test them so we don't use them in browsers where they're unsupported.
Ideally we'd have a way to do that feature testing without making Firefox blurt something out on the console. People are really sensitive about that, and no amount of reasoning will make them understand that a warning does not equate to an error. See #4774, #7291, #7535, and #10531 for example.
Change History (36)
comment:1 Changed 5 years ago by
|Component:||unfiled → attributes|
|Milestone:||None → 1.9|
|Priority:||undecided → high|
|Status:||new → open|
comment:4 Changed 5 years ago by
|Summary:||Remove/avoid deprecated attribute features → Remove Firefox deprecated nodeValue, getAttributeNode, specified|