122879 - ctrl+left, right on a wrapped line moves caret to unexpected position in a build with --enable-ctl

Status: RESOLVED INCOMPLETE

(Core :: DOM: Editor, defect, P3)

Description

[Hixie (not reading bugmail)]

STEPS TO REPRODUCE
   1. Type a line of text long enough to wrap.
   2. Press Ctrl + Left Arrow.
   3. Press Right.

EXPECTED RESULTS
   Caret should be in between the first and second letters of the last word of 
   the text.

ACTUAL RESULTS
   Caret goes to an unexpected location, namely up and right one position from 
   the end of the line.

Comment 1

[Syd Logan]

Can't duplicate, sujay? any luck?

Comment 2

[Kevin McCluskey (gone)]

Syd and I could not reproduce on Linux and WINXP.
Resolving WFM

Comment 3

[Hixie (not reading bugmail)]

I can *reliably* reproduce this on a CVS tip Linux optimised build running on
Mandrake 8.1. REOPENing. This is one of the most annoying things about Mozilla 
right now as far as I am concerned.

Please tell me how I can help track this down.

Comment 4

[Hixie (not reading bugmail)]

Note: I'm seeing this is in the <textarea> plain text editor. If you were trying
to reproduce this in Composer, that would explain why you can't see it. What is
the right component for bugs in the <textarea> plain text editor?

Comment 5

[kinmoz]

Hixie, some of us are having a problem reproducing this. Perhaps a URL to the
page you are using, or a test case (with the text you are using) would help us out.

Comment 6

[Hixie (not reading bugmail)]

the page I'm always seeing this on: 
   http://bugzilla.mozilla.org/enter_bug.cgi?product=Browser

it works with any text, but I just saw it with:
--------8<--------
adslkfjs dlfkjs lksjdf lsdkjf lsdkjf sldkjf sdlkfj sdlkfj sdlkfj sdlkfj sdlkfj
sdlkfj sdlkfj sdlkfjsdlkjfslkdf jsdlkfj sldkfj lskdjf lkj
--------8<--------

Comment 7

[Hixie (not reading bugmail)]

click on the URL link on this bug, click in the empty space at the end of the
second line, click ctrl+left arrow (should move back a word) then right arrow
(should move forward one character, but on my build, moves to the end of the
second word on the first line).

Comment 8

[Hixie (not reading bugmail)]

I just tried this with a clean profile and that didn't solve it.
I'm going to try building a clean build using the official flags tonight, see if
that fixes it.

Comment 9

[Hixie (not reading bugmail)]

Attachment: mozconfig file

Ok, I've narrowed it down to my mozconfig file (attached). With the default
config options for nightlies it works ok, but with these options I get the bug
as described above.

I'll keep investigating. I suspect the optimisation options.

Comment 10

[Hixie (not reading bugmail)]

Attachment: mozconfig file

The problem is still present when using this mozconfig file.

Comment 11

[Hixie (not reading bugmail)]

Ok, I've worked out what build option is triggering this bug:

   --enable-ctl

Comment 12

[Roland Mainz]

Prabhat, can you take a look at this one, please 

Comment 13

[Syd Logan]

If not seen in the default builds, not EDITORBASE. Sorry, have to triage down to
a list of things that most people will see.

Comment 14

[Kevin McCluskey (gone)]

Setting milestone to Moz1.1

Comment 15

[saari (gone)]

What does --enable-ctl do?

Comment 16

[Prabhat Hegde]

I believe this is a dup of 188288. --enable-ctl enables edit operation by
"Display Cell" units instead of by characters. This is particularly relevant to
Complex Text Scripts such as Hebrew, Arabic, Thai and Indic languages.

Comment 17

[Hixie (not reading bugmail)]

No, bug 188288 is a duplicate of this bug, which was filed almost exactly a year
earlier.

For the record, the patch in that bug is attachment 115149 [details] [diff] [review].

See also bug 122882, which reports another ctl text editing bug.

Comment 18

[Hixie (not reading bugmail)]

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

Comment 19

[Roland Mainz]

Ian 'Hixie' Hickson wrote:
> *** Bug 188288 has been marked as a duplicate of this bug. ***

Erm... bug 188288 has a patch for that issue - why did you mark it as a
duplicate of this one ?

Comment 20

[saari (gone)]

editorbase-

Comment 21

[Martijn Wargers (dead)]

Is this still an issue with current trunk builds?

Comment 22

[Martijn Wargers (dead)]

Is this still an issue in current trunk build?

Comment 23

[Andrei Purice]

Hey Hixie,
Can you still reproduce this issue or should we close it?

Comment 24

[Andrei Purice]

Marking this as Resolved > Incomplete since the last activity on this issue was 14 years ago and it might not be relevant anymore.
Feel free to re-open if the issue is still reproducible on your end in the latest FF versions.