192575 - wordpart1-wordpart2: caret skips whole word when it should go to the '-'

Status: RESOLVED DUPLICATE of bug 98546

(Core :: DOM: Selection, defect)

Description

[Berzelius]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
Build Identifier: 

I don't know if it applies to other languages, but when editing in Source-mode
with dutch as the language use to display content, the dash is ignored when
moving with CTRL-RightCursor through a line like:

This sentence contains a dash-skipped.

Instead the cursor skips the whole 'dash-skipped'-word, when it should go to '-'
(according to my opinion).

Reproducible: Always

Steps to Reproduce:
1.Type in source-mode: "skipped-dash"
2.Set the cursor before "skipped"
3.Press CTRL-RighCursor

Actual Results:  
The cursor jumps to after the 'h' of ...dash.

Expected Results:  
Jump before the - (like Frontpage or MS Word does). It's really anonying editing
dutch texts at the moment and really slows me down.

Comment 1

[Alfonso Martinez]

Please, always provide the build ID that you are using in order to create useful
reports.
This is WFM using 2003020704, but other people may just consider the bug invalid
due to the lack of information.

Comment 2

[Michael Lefevre]

and blocking + flags should only be set by mozilla drivers

Comment 3

[Chris Petersen]

Using the Win32 2003-02-12-08 trunk build, I can't reproduce this problem based
on the steps provided. Tested under Windows XP Pro (US English).

Comment 4

[Berzelius]

I can produce it in Mozilla 1.2.1 (Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.2.1) Gecko/20021204)

Type:

This program tries to stop-me.

Move the cursor before stop, like |stop-me
Hit CTRL - -->
the cursor is now at 
stop-me|

Maybe this is fixed in the latest builds? Will try tomorrow at work
with the latest nightly build.

Comment 5

[Kathleen :Brade]

This is a selection bug; a duplicate of bugs of there (most likely)

Comment 6

[Vaclav Dvorak]

Unless you can reproduce this with a current build, this is a duplicate of bug
98546, which is already fixed (the patch landed between 1.3a and 1.3b).

*** This bug has been marked as a duplicate of 98546 ***