Closed Bug 6033 Opened 25 years ago Closed 25 years ago

accessing ownerDocument on attribute node stops script running

Categories

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

Other
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: vidur)

References

()

Details

Accessing the ownerDocument attribute of secondA (which is an attribute node)
stops the script running, and the rest of it fails (the last few test lines
that result after pressing "Run Passive Tests") are not printed).  The line in
question is:

shouldNotBe("secondA.ownerDocument.documentElement",
secondA.ownerDocument.documentElement, "null", null);

It works if I change secondA to secondE (which is an element node), but
continues not working if I remove ".documentElement".
Status: NEW → ASSIGNED
Target Milestone: M6
I have a fix in my tree waiting to be checked in for Attribute. It's
ownerDocument is identical to that of its owning Element.

Currently, I don't really have ownerDocument implemented correctly for Elements
either. It returns the correct value when the node is attached to a document,
but null when it's free standing (i.e. when it's first created). The change to
get it to work correctly is something I want to defer till a bit later in the
cycle.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fix checked in on 5/6/1999. An attribute now returns its Element's
ownerDocument.
QA Contact: 4015 → 4078
QA Contact: 4078 → 4015
verified
Status: RESOLVED → VERIFIED
QA Contact: gerardok → gem
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.