Closed Bug 25082 Opened 21 years ago Closed 21 years ago

crash calling createContextualFragment for element with no children

Categories

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

x86
Linux
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: myk, Assigned: vidur)

References

()

Details

Overview Description: 

Steps to Reproduce: 

1) add appendSource function to Node prototype object (per article
news://news.mozilla.org/379D091F.1B5170B8%40meer.net referenced in bug 9201)
2) create a node and add it to the document tree (f.e. append it to the body
element)
3) call the appendSource method of that node

Actual Results: 

browser crashes

Expected Results: 

HTML source is parsed into document fragment, fragment is appended to dom tree,
and fragment appears in the document

Build Date & Platform Bug Found: 

2000-01-21-08 Linux

Additional Builds and Platforms Tested On: 

none

Additional Information: 

none
Changing component to DOM Level 1, which is where I think it should be, instead
of HTML frames, which is what was accidentally set on my Bugzilla report
template.
Component: HTMLFrames → DOM Level 1
Reassigning to Vidur. 
Assignee: karnaze → vidur
The crash was actually in Range::setStartAfter with a null parameter. We now 
throw an exception - the DOM spec doesn't say which one we should throw for a 
null node (though the parameter should not be null), so for now I'm throwing 
NS_ERROR_DOM_NOT_OBJECT_ERR.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
I'm not sure how QA can verify this bug. Can the reporter please mark as verified 
? Thanks.
Sorry.  It's a good reminder to me to be verifying all my fixed bugs.  This one
works as advertised.
Status: RESOLVED → VERIFIED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.