Closed
Bug 166759
Opened 22 years ago
Closed 22 years ago
setAttributeNS(xul_ns, ...) != setAttribute(...) in XUL
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: WeirdAl, Assigned: jst)
Details
Attachments
(1 file)
621 bytes,
application/vnd.mozilla.xul+xml
|
Details |
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•22 years ago
|
||
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
Closed: 22 years ago
Resolution: --- → INVALID
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.
Description
•