W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2009

[whatwg] keyboard behaviour inside of editable area

From: Alexander Surkov <surkov.alexander@gmail.com>
Date: Tue, 13 Oct 2009 09:10:17 +0800
Message-ID: <faf3cb2b0910121810v2ea46909hb380e817701c3311@mail.gmail.com>
Hi, Ian. Thank you for the answer.

AFAIK usually accessibility people tend to define kind of universal
behaviour on mouse/keyboard interaction depending on OS of course.
This case is probably not this one and behaviour should be
implementation dependent. I'm not sure. Therefore I brought this issue
for discussion.

I'm happy you find the described behaviour reasonable.

Thank you again.
Alex.


On Mon, Oct 12, 2009 at 3:04 PM, Ian Hickson <ian at hixie.ch> wrote:
> On Thu, 8 Oct 2009, Alexander Surkov wrote:
>>
>> The suggestion is to treat control element as special character, i.e.
>> when you move through the text by arrow keys and control element is met
>> then control element should be focused and its selection should be
>> changed appropriately. When control has the focus then keyboard
>> behaviour is defined by control preferences with once exception. If
>> particular navigation key isn't processed by control or doesn't have any
>> defined action then editor rules are applied.
>
> This seems reasonable (though I'd prefer to study it in a usability lab
> before making a stronger statement), but it also seems like an
> implementation detail -- there's nothing that really requires that the
> user agent even support arrow keys, let alone that they work in a
> particular way.
>
> Cheers,
> --
> Ian Hickson ? ? ? ? ? ? ? U+1047E ? ? ? ? ? ? ? ?)\._.,--....,'``. ? ?fL
> http://ln.hixie.ch/ ? ? ? U+263A ? ? ? ? ? ? ? ?/, ? _.. \ ? _\ ?;`._ ,.
> Things that are impossible just take longer. ? `._.-(,_..'--(,_..'`-.;.'
>
Received on Monday, 12 October 2009 18:10:17 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:18 UTC