- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Mon, 14 Nov 2011 16:14:03 -0500
- To: david bolter <david.bolter@gmail.com>, Larry Weiss <lweiss@microsoft.com>
- CC: Joseph Scheuhammer <clown@alum.mit.edu>, 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 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.
Yours in explicitness,
--
;;;;joseph
'I had some dreams, they were clowns in my coffee. Clowns in my coffee.'
- C. Simon (misheard lyric) -
Received on Monday, 14 November 2011 21:14:45 UTC