Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Range.surroundContent broken if start and end of range in same textnode




DOM: Core & HTML
16 years ago
3 years ago


(Reporter: peterv, Assigned: kinmoz)


Dependency tree / graph

Firefox Tracking Flags

(Not tracked)



(3 attachments, 1 obsolete attachment)



16 years ago
Calling surroundContent on a range that has its start and end boundary points in
the same textnode fails completely. The first problem is that we check if the
start boundary point is in a textnode, if so we split that node. Then we check
if the end boundary point is in a text node and we try to split that node too.
However, since we split the textnode, the end boundary point is now really in
the node created by the split, so we're using the wrong container and offset for
the end boundary point. I tried moving the split of the end boundary point
before the split of the start boundary point. Then we hit the next problem, we
try to insert the node that gets passed in to surroundContent as a child node of
the common ancestor of the start and end boundary points. Since they're in the
same textnode we seem to take that textnode as the common ancestor and so the
insert fails (textnodes can't have children). Testcase coming up.

Comment 1

16 years ago
Created attachment 78028 [details]

Comment 2

16 years ago
Created attachment 78029 [details] [diff] [review]
Partial patch

This patch just moves the splitting of the text node that contains the end
boundary point before the splitting of the text node that contains the start
boundary point. Doesn't solve all the issues.


16 years ago
Blocks: 30838
Priority: -- → P3
Target Milestone: --- → mozilla1.0.1


15 years ago
Target Milestone: mozilla1.0.1 → Future

Comment 3

15 years ago
Related bug:
Range surroundContents not implemented

Comment 4

15 years ago
I think the current implementation of SurroundContents() needs to be trashed and
then re-written to use ExtractContents() to break the "selected" content into a
subtree, InsertNode() for the new container at the collapsed point after the
extraction, and then the extracted contents inserted under the new container.

Note that ExtractContents() still doesn't work exactly as the spec dictates
because the subtree it extracts is an entirely new set of nodes representing
what was selected. See this for more details:

Comment 5

14 years ago
*** Bug 221794 has been marked as a duplicate of this bug. ***

Comment 6

14 years ago
Created attachment 133565 [details]
Testcase (fixed)

The previous test case had an infinite recursion bug.
Attachment #78028 - Attachment is obsolete: true


14 years ago
Depends on: 58974

Comment 7

14 years ago
I just posted a patch in bug 58974 that re-implements SurroundContents() and
ExtractContents(). It fixes the test case in this bug.

Comment 8

13 years ago
Created attachment 157617 [details] [diff] [review]
SurroundContents part of bug 58974

I was unable to merge all of Kin's patch to the tip, so I thought I'd just
merge the SurroundContents part of the patch, which would at least fix this
bug. Basically I applied Kin's patch, cut out SurroundContents and pasted it
into a trunk version of nsRange.cpp; it still has the ExtractContents issue

Comment 9

13 years ago
Comment on attachment 157617 [details] [diff] [review]
SurroundContents part of bug 58974

In theory I can assume r=jfrancis sr=jst right?
Attachment #157617 - Flags: superreview?(jst)
Comment on attachment 157617 [details] [diff] [review]
SurroundContents part of bug 58974

Yeah, seems reasonable to me.
Attachment #157617 - Flags: superreview?(jst) → superreview+

Comment 11

13 years ago
Fix checked in.
Last Resolved: 13 years ago
Resolution: --- → FIXED

Comment 12

12 years ago
I wonder if this bug has rell been resolved. I get the same issue today, with:

Mozilla 1.7.12
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051022


Firefox 1.0.7
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060106 Firefox/1.0.7

and it's 2006! the bug was suppsedly solved in 2004...?

Comment 13

12 years ago
I wonder why can't one re-open a bug...

Comment 14

12 years ago
Don't reopen this bug, it is fixed in Firefox 1.5 and trunk. It was never fixed on the 1.0.x branch (and there's no need to do so). If you still see the issue on a trunk build, open a new bug.
Component: DOM: Traversal-Range → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.