241486 - Input soft hyphens cause textareas to misplace text cursor position

Status: RESOLVED DUPLICATE of bug 289857

(Core :: Layout: Form Controls, defect)

Description

[Ernest Cline]

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

The presence of soft hyphens in a textarea causes the location where text input
occurs and where the text cursor is displayed to not be the same on the line of
text after the soft hyphen.

Reproducible: Always
Steps to Reproduce:
1. Input text that contains a soft hyphen into a textarea.
2. Use the left arrow key to go back one position.  (Only one position is
needed, no matter how far away the soft hyphen is.)
Actual Results:  
The place where input now occurs is one character previous to where the cursor
is displayed.  It also impossible to use the right arrow key to cause the place
where text input occurs to be at the end of that line.


Expected Results:  
Input should occur where the cursor is displayed.

I first noriced this with 1.6 during the 1.7b test period, but given the minor
nature of this bug I waited until I had downloaded a new version in hopes you
had fixed the problem.

This is probably related to the other soft hyphen bugs, but might not be
dependent upon their being fixed in order to be fixed itself.  The root cause
appears to be that when the text cursor is not at the end of a line, it is
counting the soft hyphen when determing where text input occurs in the line, but
not in determining where the text cursor is displayed.  One could argue that in
a textarea that a soft hyphen should always be displayed (perhaps with a change
in background color to indicate its special status) but that is clearly
secondary to just simply getting the text cursor to work correctly.

Comment 1

[Mark R. Bannister]

Attachment: testcase for soft hyphen bug in textarea

Comment 2

[Mark R. Bannister]

I've added a testcase for this one, I'm reproducing it on Windows build 2004052709.

Comment 3

[Jesiah S]

I see this on LInux 2004060105

Comment 4

[rbs]

Can't reproduce this anymore. May have been fixed by the patch for bug 289857.

Comment 5

[Uri Bernstein]

(In reply to comment #4)
> Can't reproduce this anymore. May have been fixed by the patch for bug 289857.

Yes, it was fixed by that patch (this is essentially a dup).

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