Bug 31229 - Cursor movement is confused by excess whitespace
Summary: Cursor movement is confused by excess whitespace
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-07 13:17 PST by Chris Ridd
Modified: 2010-06-07 23:30 PDT (History)
1 user (show)

See Also:

Attachments
Example (210 bytes, text/html)
2009-11-07 13:17 PST, Chris Ridd 		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 Ridd 2009-11-07 13:17:24 PST 
Created attachment 42700 [details]
Example

A combination of excess whitespace and inline elements seems to confuse keyboard cursor motion.

Reproduce:

1. In the attached example, click after the text "Add".

2. Press cursor left 7 times. The cursor should be in front of the "a" in "Panel".

3. Press cursor left again.

Expected Result:

The cursor moves to the left of "P".

Actual Result:

The cursor moves *right* to after the "l" in "Panel".

(Cursoring left again will loop again when it goes past the "a".)

Workarounds:

Removing the excess whitespace in between "Control" and "Panel" fixes the problem. However, removing the spans (and leaving the whitespace) also fixes the problem, so there's something more subtle going on.
Comment 1 Robin Qiu 2010-05-26 01:23:14 PDT 
I checked this bug, it was fixed in ToT.
Comment 2 Chris Ridd 2010-05-26 07:35:31 PDT 
(In reply to comment #1)
> I checked this bug, it was fixed in ToT.

Agreed, it seems to be fixed in WebKit build 533.4, which is what Google Chrome 5.0.375.55 is using.

WebKit build 531.22.7, which is what Safari 4.0.5 is using, still has the bug.

Thanks for checking :-)
Comment 3 Chris Ridd 2010-06-07 23:30:42 PDT 
(In reply to comment #2)
> (In reply to comment #1)
> > I checked this bug, it was fixed in ToT.
> 
> Agreed, it seems to be fixed in WebKit build 533.4, which is what Google Chrome 5.0.375.55 is using.
> 
> WebKit build 531.22.7, which is what Safari 4.0.5 is using, still has the bug.
> 
> Thanks for checking :-)

(Final comment)

The bug is also fixed in Safari 5 using WebKit build 533.16.