W3C home > Mailing lists > Public > public-html@w3.org > December 2010

Re: role=presentation must not be applied to focusable elements

From: Maciej Stachowiak <mjs@apple.com>
Date: Sat, 25 Dec 2010 17:19:00 -0700
Cc: HTMLWG WG <public-html@w3.org>
Message-id: <ACCBA5DB-C1DA-478F-9DB7-2C5983DF45BE@apple.com>
To: Ian Hickson <ian@hixie.ch>

On Dec 25, 2010, at 11:56 AM, Ian Hickson wrote:

> On Thu, 23 Dec 2010, Maciej Stachowiak wrote:
>> HTML5 doesn't actually define the effect of being focusable. Is that 
>> list the suggested list of things that should get focus when 
>> mouse-clicked, or tapped on a touch device? Is it the set of things that 
>> gets focus when you call their focus() method? Are these two sets 
>> allowed to be different?
> This is all defined in the spec (yes, yes, yes, and yes, respectively). 

If "focusable" implies both mouse-focusability (or touch-focusability) and programmatic focusability, yet an element is allowed to have one but not the other, then it seems there are possible states for elements that are not described by the spec.

> The one thing that isn't defined is the most important part of focusing: 
> that when something is focused, key events go there. However, this is just 
> because the spec doesn't define key events in the first place.

Good point. What spec should define this? Should DOM Events incorporate the concept of focus?


Received on Sunday, 26 December 2010 00:19:46 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:28 UTC