Bug 41162 - [GTK] Cannot change the selection via the keyboard
Summary: [GTK] Cannot change the selection via the keyboard
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-24 09:17 PDT by Martin Robinson
Modified: 2010-06-24 17:29 PDT (History)
1 user (show)

See Also:


Attachments
Fix for this issue (4.12 KB, patch)
2010-06-24 10:58 PDT, Martin Robinson
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Robinson 2010-06-24 09:17:08 PDT
After selecting some text in a non-editable area, it should be possible to change the selection by holding down the shift key and arrow keys. This doesn't work in the GTK+ port.
Comment 1 Martin Robinson 2010-06-24 10:58:50 PDT
Created attachment 59679 [details]
Fix for this issue
Comment 2 Xan Lopez 2010-06-24 13:49:03 PDT
Comment on attachment 59679 [details]
Fix for this issue

So we are changing the logic a bit here, before we were allowing all kinds of events if caret mode was enabled. Are you changing that on purpose?
Comment 3 Martin Robinson 2010-06-24 14:49:41 PDT
Yes. Before we were only allowing editor commands:

1. If the node was editable.
2. If caret browsing was enabled.

This patch enables editor commands:

1. If the commands don't insert text (includes all caret browsing commands, AFAIK).
2. The command inserts text and the node is editable.

I think this new logic is more precise. The only change that I can see is that previously a caret browsing command that inserted text (if such a beast existed) could operate on a non-editable node. I think disallowing that is a better behavior here.
Comment 4 Xan Lopez 2010-06-24 15:07:57 PDT
(In reply to comment #3)
> Yes. Before we were only allowing editor commands:
> 
> 1. If the node was editable.
> 2. If caret browsing was enabled.
> 
> This patch enables editor commands:
> 
> 1. If the commands don't insert text (includes all caret browsing commands, AFAIK).
> 2. The command inserts text and the node is editable.
> 
> I think this new logic is more precise. The only change that I can see is that previously a caret browsing command that inserted text (if such a beast existed) could operate on a non-editable node. I think disallowing that is a better behavior here.

Right, this is how I understood the patch but wanted to double-check it was intentional. I don't think there's such a thing as a text inserting caret command, no :)
Comment 5 Xan Lopez 2010-06-24 15:08:12 PDT
Comment on attachment 59679 [details]
Fix for this issue

r=me
Comment 6 Martin Robinson 2010-06-24 17:29:40 PDT
Comment on attachment 59679 [details]
Fix for this issue

Clearing flags on attachment: 59679

Committed r61808: <http://trac.webkit.org/changeset/61808>
Comment 7 Martin Robinson 2010-06-24 17:29:44 PDT
All reviewed patches have been landed.  Closing bug.