231123 - doubleclick on word before a link. First word in link is marked as well.

Status: RESOLVED EXPIRED

(Core :: DOM: Selection, defect)

Description

[Peter Brodersen]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

In a case of text like foo bar baz where bar baz is a link, a doubleclick on the
word "foo" will result in selection of "foo bar", not only "foo".

"Baz" is not needed to reproduce the problem. The link URL is not important.


Reproducible: Always

Steps to Reproduce:
1. Make code like: <p>Foo <a href="http://www.google.com">Bar Baz</p>
2. Doubleclick on Foo


Actual Results:  
"Foo Bar" gets selected

Expected Results:  
Only "Foo" should be selected

Tested at WinXP, moz1.6b and moz1.6.

Error also occurs at Win2000, moz1.5a.

Haven't tested on other platforms.

Comment 1

[Peter Brodersen]

Minor typo... the bug also appears in valid (X)HTML :)

<p>Foo <a href="http://www.google.com">Bar Baz</a></p>

Or: http://stock.ter.dk/doubleclick.php

Comment 2

[Jordan C.]

Happens in Firebird 0.7 too. Foo Bar_ is highlighted (meaning Foo, Bar, and the
space between Bar and Baz.)

Comment 3

[Peter Brodersen]

It seems like it happens at any word followed by any tag - it doesn't have to be
an anchor.

E.g. when doubleclicking on "Status" in "Status Whiteboard" (present at this
bug-page), both words gets marked.

Test:
1. Create page with <b>Status <u>W</u>hiteboard:</b>
2. Doubleclick on "Status"

Comment 4

[Erik Fabert]

*** Bug 263458 has been marked as a duplicate of this bug. ***

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 7

[dnmiller]

but it's still there