58213 - selectNode returns same as selectNodeContents

Status: VERIFIED INVALID

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

Description

[Dylan Schiemann]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20001009
BuildID:    2000100908

The DOM 2 Range method selectNode() is expected to return a node, but instead
returns the contents of the node, which is what would be expected instead for
selectNodeContents.

Reproducible: Always
Steps to Reproduce:
1. Create Range
2. Range.selectNode(in Node n)
3. Range contains text, not a node

Actual Results:  Returns contents

Expected Results:  Returns a node

testcase to follow

Comment 1

[Dylan Schiemann]

Attachment: testcase

Comment 2

[Johnny Stenback (:jst)]

Anthony, one more range bug for you.

Comment 3

[Doron Rosenberg (IBM)]

reporter: are you still seeing this on new builds?

Comment 4

[anthonyd]

I'll work on this, no problem, but why am I suddenly getting Range bugs assigned 
to me?

anthonyd

Comment 5

[anthonyd]

ignore my previous comment, i guess editor is responsible for range, oops!

anthonyd

Comment 6

[Dylan Schiemann]

I see the same problem in 20001031
on Win2k... the testcase should be returning a node, but is instead returning
the node contents.

There is an increase in Range bugs as I went through the Range spec last week
and tested each method and attribute... jst said to assign them to you.  Should
I post individual bugs for each of the non-implemented Range features, or leave
them as the the one general bug,
http://bugzilla.mozilla.org/show_bug.cgi?id=30838 ?

Comment 7

[anthonyd]

Dylan,

The general rule is one issue one bug, one bug that says fix all of range, 
is/might be really more than one issue.  Please go ahead and file a bug against 
ME on each range bug you fine.

Thanks,
anthonyd

Comment 8

[Doron Rosenberg (IBM)]

confirmign bugs per reporter

Comment 9

[anthonyd]

Dylan,
range.selectNode() and selectNodeContents() are setting the range correctly.  In 
your sample file the alert call is converting the range to a string.  the 
toString call does not print block elements (ie. <p> or <div>) just the 
contents.

attaching test case to demonstrate.

Comment 10

[anthonyd]

Attachment: test case

Comment 11

[anthonyd]

resolving bug as invalid

anthonyd

Comment 12

[Dylan Schiemann]

I see, I did not know that alert would not print block level elements.  Is that
conversion on purpose, or a bug/limitation of alert() ?

Comment 13

[anthonyd]

it just calls toString.

anthonyd

Comment 14

[Fabian Guisset]

VERIFIED invalid