Bug 55970

Summary: Cursor disappears from textarea on certain occasions.
Product: WebKit Reporter: Cngevpxhaqrefpber <Cngevpxhaqrefpber>
Component: HTML EditingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: adele, ap, enrica, hyatt, leviw, mitz, rniwa, xji
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
demo none

Cngevpxhaqrefpber
Reported 2011-03-08 14:40:12 PST
If you: 1. Set focus to a textarea with no text on it. 2. Type a bunch of characters (I was using spaces) until you get two characters from the right side edge/boundary of the textarea. 3. Type a letter (like 'a'), then press the space bar. Then the cursor disappears in both Safari (latest version) and Google Chrome 10.0.648.127 (Official Build 76697), which doesn't seem right. One thing I did notice is, if the textarea has a vertical scrollbar visible (I did this by inserting a bunch of empty lines) and you follow the same steps above, then the cursor does not disappear, _unless_ you're typing on the very last line of the textarea.
Attachments
demo (216 bytes, text/html)
2011-03-09 11:45 PST, Ryosuke Niwa 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Ryosuke Niwa
Comment 1 2011-03-09 11:45:31 PST
Created attachment 85207 [details] demo
Xiaomei Ji
Comment 2 2011-03-10 15:54:35 PST
might be the same cause as bug 49508 which I am working on. looks like my fix fixes this issue as well.
Xiaomei Ji
Comment 3 2011-03-18 17:02:42 PDT
*** This bug has been marked as a duplicate of bug 49508 ***
Xiaomei Ji
Comment 4 2011-04-08 18:32:08 PDT
I am not so sure that this is a duplicate of bug 49508. The fix there fixed the problem in Safari in Mac, but not fixed for chromium Linux. There might be some other problems.
Ryosuke Niwa
Comment 5 2011-05-02 13:25:14 PDT
The caret / insertion point is rendered outside of the visible bound. The related bugs: http://webkit.org/b/57745 and http://webkit.org/b/54598.
Enrica Casucci
Comment 6 2011-05-02 15:58:48 PDT
This has been fixed by http://trac.webkit.org/changeset/85535
Note You need to log in before you can comment on or make changes to this bug.