Closed
Bug 598877
Opened 14 years ago
Closed 14 years ago
.firstChild returns null for attributes even when .value has been set
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla2.0b7
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | final+ |
People
(Reporter: mounir, Assigned: mounir)
References
Details
(Keywords: regression, testcase)
Attachments
(2 files)
|
300 bytes,
text/html
|
Details | |
|
2.54 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
This is a regression caused by bug 566416.
Tonight while Blake and I were debugging, Blake point this interesting bug in nsDOMAttributes. If you create an attribute and set its value then query for the firstChild, it will be null while it's the text node of the value in 3.6.
|
Assignee | |
Updated•14 years ago
|
Summary: .firstChild returns null on attributes even when .value has been set → .firstChild returns null for attributes even when .value has been set
|
|
Assignee | |
Comment 1•14 years ago
|
||
All credits to Blake for this patch.
Attachment #477874 -
Flags: review?(bzbarsky)
|
||
Comment 2•14 years ago
|
||
Comment on attachment 477874 [details] [diff] [review]
Patch v1
OK, but we really need to get rid of all this "attribute node" junk. :(
Attachment #477874 -
Flags: review?(bzbarsky) → review+
|
|
Assignee | |
Comment 3•14 years ago
|
||
This should block considering it's a regression.
blocking2.0: --- → ?
|
||
Updated•14 years ago
|
blocking2.0: ? → final+
|
|
Assignee | |
Updated•14 years ago
|
Blocks: CVE-2010-3766
|
|
Assignee | |
Comment 4•14 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b8
|
||
Updated•14 years ago
|
Target Milestone: mozilla2.0b8 → mozilla2.0b7
You need to log in
before you can comment on or make changes to this bug.
Description
•