W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2004

[whatwg] [web-forms] Add ACCESSKEY to SELECT

From: Matthew Raymond <mattraymond@earthlink.net>
Date: Fri, 13 Aug 2004 16:29:40 -0400
Message-ID: <411D24B4.5030309@earthlink.net>
Anne van Kesteren wrote:

>>    Could you please post a link to the email you refer to, or the 
>> original example, that shows a situation where <label> and its 
>> corresponding |accesskey| attribute cannot be associated with a 
>> control to provide an access key for that control. I myself cannot 
>> think of a situation where that is the case.
> 
> 
> I can[1].
[Snip!]
> [1]<http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2004-August/001703.html> 

    From that link:

---------------------------------------------------
How can the optional attributes of LABEL affect the optional attributes
of SELECT? INPUT has an ACCESSKEY attribute as well, we are not going to
remove it from that element either, do we?

For example, you could have datagrid like:

   <table>
    <thead>
     <tr><th>Foo</th><th>Bar</th>
    </thead>
    <tbody>
     <tr><td><select/></td><td><input/></td></tr>
     <tr><td><select/></td><td><input/></td></tr>
    </tbody>
   </table>
---------------------------------------------------

    For the first question in that message, the |accesskey| attribute 
gives focus to the <label> when the access key is pressed, and the 
<label> element then passes focus to the associated control. Therefore, 
the <label> element effectively becomes the |accesskey| attribute for 
the <select>.

    To address the second question, we clearly need to leave |accesskey| 
as part of <input> for backwards compatibility. For consistency sake, 
|accesskey| should probably be added as well, now that I think of it, 
but that doesn't mean it can't enter the specification already depreciated.
Received on Friday, 13 August 2004 13:29:40 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:36 UTC