setAttributeNS(xul_ns, ...) != setAttribute(...) in XUL

VERIFIED INVALID

Status

()

Core
DOM: Core & HTML
VERIFIED INVALID
16 years ago
10 years ago

People

(Reporter: WeirdAl, Assigned: jst)

Tracking

Trunk
x86
Other
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

621 bytes, application/vnd.mozilla.xul+xml
Details
(Reporter)

Description

16 years ago
I've been working with XUL recently, and I've noticed a discrepancy between 
setAttribute() and setAttributeNS() when the latter uses the XUL namespace 
anyway.  I have a testcase, and have confirmed Mozilla 1.1b flunks the testcase.
(Reporter)

Comment 1

16 years ago
Created attachment 97898 [details]
Testcase

Expected results:  You should see a complete sentence after the page loads.

Actual results:  Incomplete sentence.
setting attributes in the xul namespace is not the same as setting them in the
null namespace, so

<xul:description value="text"/>

is not the same as

<xul:description xul:value="text"/>

the former sets the attribute in the nullnamespace, the latter in the xul
namespace. The same applies when using the DOM. This in complience to the XML
spec, the XML-namespace spec and the DOM spec.

Most applications, xul included, uses attributes in the null namespace.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
(Assignee)

Comment 3

16 years ago
Invalid indeed.
Status: RESOLVED → VERIFIED

Updated

10 years ago
Component: DOM: Core → DOM: Core & HTML
QA Contact: stummala → general
You need to log in before you can comment on or make changes to this bug.