Re: accesskey

Michael Hamm wrote:
> 
> On Mon, 27 Dec 1999, Eric Eldred wrote, in part:
> > > Looking at XHTML1[1] and HTML4.01[2], I note again[3] that <link> has no
> > > accesskey attribute, and I ask again: why not? Oughtn't it?
> > >
> > maybe it should also have a "tabindex" attribute
> > as well, then.<snip>
> > since the big 2 browsers don't seem to
> > implement LINK for nav bars, we would foul
> > up the order of accesskey retrieval (the
> > LINK nav element would not be accessed, one
> > has to assume, if it isn't displayed).
> 
> So it would seem from the Spec ("Pressing an access key assigned to an
> element gives focus to the element."[3]), but I see no reason that that
> should be so. Why shouldn't a <link>, even if not displayed, have an
> accesskey?

You allude to the problem. Noting that <link> may be used for various 
features, some of which have no user interaction at all, what exactly
would the accesskey being pressed *do*? If it's not intuitive it's 
unlikely that we'd want to suggest it.

Unless there is an intuitive association between a link element and
an intended behaviour, adding an accesskey is going to introduce more
problems than it solves. And one must note that there are many kinds
of links;, not all involve user interaction.

Murray

...........................................................................
Murray Altheim                                   <mailto:altheim@sonic.net>
Member of Technical Staff, Tools Development & Support
Sun Microsystems, Inc. MS MPK17-102
1601 Willow Rd., Menlo Park, California 94025  <mailto:altheim@eng.sun.com>

   the honey bee is sad and cross and wicked as a weasel
   and when she perches on you boss she leaves a little measle -- archy

Received on Monday, 27 December 1999 13:45:16 UTC