Bug 9592 - REGRESSION: Can't navigate caret to the beginning of next line in a textarea
Summary: REGRESSION: Can't navigate caret to the beginning of next line in a textarea
Status: RESOLVED DUPLICATE of bug 9528
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P1 Major
Assignee: Nobody
URL:
Keywords: InRadar, Regression
Depends on:
Blocks:
 
Reported: 2006-06-25 22:06 PDT by Chris Petersen
Modified: 2006-06-26 08:22 PDT (History)
1 user (show)

See Also:

Attachments
TEXTAREA sample file (234 bytes, text/html)
2006-06-25 22:09 PDT, Chris Petersen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Petersen 2006-06-25 22:06:00 PDT 
* SUMMARY
With a textarea that is pre-populated with text, I can't place the caret to the beginning of the next line

* STEPS TO REPRODUCE
1. Open test case "textarea_sample.html" in a TOT webkit nightly build
2. Place the caret at the beginning of word "Banana" in the textarea sample 1
3. Press the down arrow key which should place the caret in the next line below "Banana" However, the caret is actually placed at the END of the word "Banana" (wrong)

Another example is to place the caret at the end of "Street Address" in textarea sample. Then press ctrl - left arrow keys. This should place the caret at the BEGINNING of this line "Street Address". But instead, the caret appears at the end of the above line "Full Name".


* RESULTS
Caret should appear at the beginning of the next or current line but doesn't.

* REGRESSION
Yes, this is working in 10.4.6 and looks like a regression with the new native textarea fields.  
Comment 1 Chris Petersen 2006-06-25 22:09:00 PDT 
Created attachment 9039 [details]
TEXTAREA sample file
Comment 2 Chris Petersen 2006-06-25 22:10:47 PDT 
This issue is filed in radar as 4601142.
Comment 3 David Kilzer (:ddkilzer) 2006-06-26 03:57:03 PDT 
I think this is a duplicate of (or closely related to) Bug 9528.
Comment 4 Darin Adler 2006-06-26 08:22:11 PDT 
Yes, it is a duplicate.

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