Dave Booth Reporter
	Description • 21 years ago

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6b) Gecko/20031210
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6b) Gecko/20031210

Problem exists whilst composing mail, whilst typing in a text widget on a web
form (such as this one) and in almost every other situation where text is
autowrapped by mozilla. Up/Down cursor keys move the caret as one ould expect -
directly up or down one line, or as near to it as one can get given the length
of the line being moved to. Right/Left on the other hand misbehave - in the
first line of any autowrapped paragraph they appear to work normally but as soon
as one passes the autowrap point left-arrow moves the caret to the beginning of
the previous line (or in some cases to the beginning of the paragraph) and
right-arrow moves to the beginning of the next line. Problem goes away if line
breaks are manually inserted or, in the case of composing email, if the user
performs Edit>Rewrap. It appears that the linebreaks inserted by rewrap are
equivalent to manual paragraph breaks. As soon as any autowraps occur as a
result of further editing, the problem behaviour recurs within the autowrapped
segment of text. Home and End keys work as expected, moving the caret to the
beginning and end of the current line.

Reproducible: Always

Steps to Reproduce:
1. Find a web form with a multiline text box or compose a new plaintext email.
2. Type text until you have 3 or 4 autowrapped lines.
3. Use the mouse to place the caret in the middle of the text.
4. Use the right and left cursor keys to navigate the current line.
Actual Results:  
Other than on the first line of an autowrapped paragraph, right and left cursor
keys misbehave as described.

Expected Results:  
Right and left cursor keys should move the caret by a single character.

	Dave Booth Reporter
	Comment 1 • 21 years ago

May be an old ctl problem and therefore a dup of bug 122879 or bug 188288 - I
just noticed that the contributed solaris build (the one I'm running) has ctl
enabled and theres plenty of bug reports on that feature! I'm going to see if I
can get access to a box with the forte compilers and build one with the same
options but with ctl disabled and see if the problem goes away...

This may take me a while - it was why I grabbed a contrib build rather than
building it myself in the first place. If somebody else has the resources
available to do this triage step they will likely beat me to it.

	Dave Booth Reporter
	Comment 2 • 21 years ago

to heck with it - found the main ctl bug report - marking dup.

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