Closed
Bug 295677
Opened 20 years ago
Closed 13 years ago
uncaught exception with range.commonAncestorContainer in this case with removed nodes
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: martijn.martijn, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
|
531 bytes,
text/html
|
Details |
With the upcoming testcase, I get this js error in the console:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIDOMRange.commonAncestorContainer]" nsresult:
"0x80004005 (NS_ERROR_FAILURE)" location: "JS frame ::
file:///C:/Documents%20and%20Settings/mw22/Bureaublad/x.htm :: <TOP_LEVEL> ::
line 13" data: no]
I would have expect an alert box with the text "two".
| Reporter | ||
Comment 1•20 years ago
|
||
Comment 2•20 years ago
|
||
You remove the boundary points of the range from the document, and then expect
to find some common ancestor container? The removed nodes have no relation to
each other, either. INVALID.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 3•20 years ago
|
||
I filed this bug based on this discussion:
http://groups.google.nl/group/netscape.public.mozilla.dom/browse_thread/thread/ea74d4ca38fec8c8/47fbdddff8273ebc?q=range&rnum=3&hl=nl
Comment 4•20 years ago
|
||
Yep. This is a valid bug report. Please read the code and the spec again
carefully, Alex.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 5•18 years ago
|
||
It should fail on the first SetXXX() call, since the nodes aren't in a Document, DocumentFragment, or Attr node. So this is a bug, but not quite the reported one.
Updated•16 years ago
|
Assignee: traversal-range → nobody
QA Contact: ian → traversal-range
Comment 6•13 years ago
|
||
It alerts "two" for me now. This should be tested, though.
Status: REOPENED → RESOLVED
Closed: 20 years ago → 13 years ago
Flags: in-testsuite?
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•12 years ago
|
Component: DOM: Traversal-Range → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•