Bug 17961 - Webkit has trouble arrowing through <wbr>s with keyboard
Summary: Webkit has trouble arrowing through <wbr>s with keyboard
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 525.x (Safari 3.1)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: GoogleBug
Depends on:
Blocks:
 
Reported: 2008-03-19 17:28 PDT by Ojan Vafai
Modified: 2008-12-29 14:23 PST (History)
2 users (show)

See Also:


Attachments
Test-case (274 bytes, text/html)
2008-03-19 17:29 PDT, Ojan Vafai
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ojan Vafai 2008-03-19 17:28:36 PDT
Will provide description + test-case.
Comment 1 Ojan Vafai 2008-03-19 17:29:39 PDT
Created attachment 19891 [details]
Test-case
Comment 2 Ojan Vafai 2008-03-19 17:30:32 PDT
Follow the instructions on the test page. Can't select past the WBR using the keyboard. Tested on Safari 3.1 on Windows and Mac.
Comment 3 Gavin Sherlock 2008-03-19 19:54:15 PDT
Interestingly, if, after you place your cursor on the top line, you use the right arrow key to go through the text, it will have a problem at the <wbr>, but you can get past it.  Once you have gone past the <wbr>, you are now able to select the text as described in the test case.
Comment 4 Peter Kasting 2008-03-20 10:54:08 PDT
Note that this bug makes deleting chunks of text in e.g. Gmail frustrating (once you know the right-arrow workaround you can bypass the bug, but it constantly gets in your way).

This is so irritating so often (daily) to webmail users like me that I request this be raised back to P2.
Comment 5 Ojan Vafai 2008-03-20 10:58:41 PDT
I agree, this is a pretty bad experience and it's surprisingly common to get WBRs in emails.
Comment 6 Peter Kasting 2008-03-21 13:35:19 PDT
This actually affects more than just selection.  In the testcase on this bug, simply click in the top of the box and use the down arrow to move down.  You get stuck at the wbr, just like if you were holding shift.  So I think the underlying problem is in the "move down one line" handling.
Comment 7 Robert Blaut 2008-12-29 14:23:16 PST
I tested today attached test case in WebKit r39474 and I cannot reproduce the issue anymore.

Bisect-builds tells me that the bug was fixed between  r38860 and r39005.