Closed Bug 6073 Opened 25 years ago Closed 25 years ago

Node::childNodes should never be null

Categories

(Core :: DOM: Core & HTML, defect, P3)

Other
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: vidur)

References

()

Details

Node::childNodes should never be null. If a node has no children, it should be a nodelist with no nodes in it. See the above test ("Run Passive Tests"), and the DOM spec: http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-1950641247
QA Contact: 4015 → 4078
Status: NEW → ASSIGNED
Target Milestone: M8
Yup. It's just laziness on my part. Since this isn't breaking anyone, I'm moving it to M8.
Target Milestone: M8 → M10
I have a question into the DOM WG, since I believe it might be a mistake that the spec requires that all nodes (even those that can't have children) have a childNodes list under them. My recollection is that we decided that all *elements* should always return a valid childNodes list, but I think it might have inadvertantly been written up as all nodes. Pushing off the bug till I get an answer.
Node::getAttributes() does the same thing
Yes, but Node::getAttributes() does that as per spec. It should return null for all but Elements.
I have a fix in my tree. Still waiting for the tree to be open and green at a point where I'm ready to check in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fix checked in on 8/25/1999.
QA Contact massive update.
Verified fixed, Linux apprunner 1999-10-08-08-M11.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.