W3C home > Mailing lists > Public > wai-xtech@w3.org > November 2011

Re: Bug 14320 as discussed in Re: [aapi] UAI TF Meeting Minutes, November 8, 2011

From: david bolter <david.bolter@gmail.com>
Date: Mon, 14 Nov 2011 16:17:59 -0500
Message-ID: <CAEO7jQBz1F2RP2dEUO9mteoq7EfDKugGqiDidcXH2sd+knU1Wg@mail.gmail.com>
To: Joseph Scheuhammer <clown@alum.mit.edu>
Cc: Larry Weiss <lweiss@microsoft.com>, Cynthia Shelly <cyns@microsoft.com>, Andi Snow-Weaver <andisnow@us.ibm.com>, David Bolter <dbolter@mozilla.com>, Matthew King <mattking@us.ibm.com>, Stefan Schnabel <stefan.schnabel@sap.com>, "Surkov, Alexander" <surkov.alexander@gmail.com>, "wai-xtech@w3.org" <wai-xtech@w3.org>
On Mon, Nov 14, 2011 at 4:14 PM, Joseph Scheuhammer <clown@alum.mit.edu>wrote:

> On 11-11-14 4:08 PM, david bolter wrote:
>> Thanks Larry.
>> Here's a fun tricky case:
>> In the case where there is an editable field, which has a some text "fo"
>> followed by a blinking text entry bar, and there is a drop down of
>> autocompletions such as "foo" "food" "fox"... etc, and in addition to this
>> it is possible to up and down arrow to move the selection highlight among
>> the completions, where is visual keyboard focus?
> Not tricky enough, or, it's just implicit:  add the fact that any
> characters that the user types are shown in the text field.  Using your
> example, starting with "fo":  if the user types an 'o', the text field
> becomes "foo" followed by a blinking cursor.  Also, left and right arrows
> move among the characters in the text field.  Yet another also,
> shift+left/right arrows select characters in the text field.
I would agree, but this seems to be a counter example to the visible
keyboard focus being the active child. You cut off the relevant related bit
of Larry's email though :)

Received on Monday, 14 November 2011 21:18:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:44 UTC