Closed Bug 313413 Opened 19 years ago Closed 19 years ago

double-click between word and trailing space selects next word as well

Categories

(Core :: DOM: Selection, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 200098

People

(Reporter: eric, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051005 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051005 SeaMonkey/1.1a

In Mozilla 1.7.5, double-clicking a word selected just the word, and
double-clicking between the word and the trailing space selected the word and
the trailing space (handy for cutting and pasting it elsewhere in, say, an
e-mail message or web comment form).

In SeaMonkey 1.0a, double-clicking between a word and the trailing space also
selects the next word.

Reproducible: Always

Steps to Reproduce:
In e-mail composition window, web comment form, or any window with selectable
text, double-click at the end of a word that is followed by a space.
Actual Results:  
The next word is selected along with the desired word and trailing space.

Expected Results:  
Only the targeted word and the trailing space should be selected.
Hmm, I see this with recent firefox/seamonkey nightly (Mac OS 10.3.9). The old
behaviour was that if you double-clicked in the left part of the space, the next
word was not selected. Now, both words are selected. Marking New, since I don't
seem to find any dupes.
Assignee: mail → selection
Status: UNCONFIRMED → NEW
Component: MailNews: Main Mail Window → Selection
Ever confirmed: true
Product: Mozilla Application Suite → Core
Version: 1.7 Branch → Trunk
This has already been reported as bug 200098.

*** This bug has been marked as a duplicate of 200098 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
(In reply to comment #2)
> This has already been reported as bug 200098.

The point is that the behaviour has changed since the 1.7 branch. But I'll comment in 200098 instead.
You need to log in before you can comment on or make changes to this bug.