Closed Bug 393222 Opened 12 years ago Closed 9 years ago
.prefix when it is 'null' should have no effect
User-Agent: Opera/9.20 (Windows NT 5.1; U; nb) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20070725 Firefox/22.214.171.124 Quoting the DOM3 Core spec: > prefix of type DOMString, introduced in DOM Level 2 > The namespace prefix of this node, or null if it is unspecified. > When it is defined to be null, setting it has no effect The way I interpret that, "prefix" is basically read-only when it is null, so that after setting it, it remains null. This is what Opera does (refer to Opera bug 160678, which is invalid if this bug isn't :) ) but not what Firefox does. It is not entirely clear to me what the spec means by "have no effect" but for cross-browser compatibility it should be clarified. Reproducible: Always
Node.prefix is now readonly in spec and implementation.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.