Closed Bug 3925 Opened 26 years ago Closed 26 years ago

TEXTAREAs' default cursor location can be improved

Categories

(Core :: Layout, enhancement, P3)

All
Windows NT
enhancement

Tracking

()

VERIFIED INVALID

People

(Reporter: cpratt, Assigned: kmcclusk)

Details

Using the following HTML snippet: <form action="mailto:Kligor.T@gee.whiz.com"> <textarea rows="10" cols="40"> </textarea> apprunner displays a text input control in the browser. However, when you click into it, behavior is different among platforms and in no case ideal. On Windows, the cursor shows up not at the upper left hand corner of the text area, but near the middle of the top row, and there appears to be a tab to the left of it (that is, you can press the left arrow key to go to the upper left hand corner). On the Mac, clicking into the text area places the insertion point about a space to the right of the expected upper left hand corner position, and you can press the left arrow key to go there. If it's possible, please change this so that clicking into a textarea always places the cursor in the upper left hand corner of the area, and so that there are no tabs or spaces in the area.
Assignee: troy → karnaze
Assignee: karnaze → kmcclusk
Kevin, we may want to hold off on this one until after we get Ender unless it is easy.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
We have the same behavior in Communicator and I believe that the differences you have seen between Mac and Windows come from differences in the sample HTML snippet that you were using on the two platforms. The spaces that you were seeing correspond to the spaces before the </textarea> tag. I guess that on windows, you had 8 spaces (that's why the cursor was near the middle of the top row) while on the Mac, you had 1 or 2 tabs at the same location (that's why the cursor was closer to the upper left hand corner position). If you want to avoid the problem, use the following HTML snippet: <form action="Kligor.T@gee.whiz.com"> <textarea rows="10" cols="40"></textarea> Closed as Invalid.
Status: RESOLVED → VERIFIED
Right you are! Thanks for the explanation. Marking verified invalid.
You need to log in before you can comment on or make changes to this bug.