W3C home > Mailing lists > Public > public-svg-wg@w3.org > July to September 2012

tabindex in SVG2 (was: Re: id's in the SVG2 spec)

From: Cameron McCormack <cam@mcc.id.au>
Date: Mon, 30 Jul 2012 08:55:42 +1000
Message-ID: <5015BF6E.9000209@mcc.id.au>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
CC: SVG public list <www-svg@w3.org>
[Changed subject line, since this was originally about the presence of 
IDs in the spec itself, not IDs and focusability of SVG content.  Also 
moved the discussion to www-svg@w3.org, where we should have technical 
discussions.]

Richard Schwerdtfeger:
> One of the things we will need to add in SVG2 is tabindex for keyboard
> navigation so that we can have a consistent keyboard navigation model
> between HTML and SVG. In HTML all elements with the body that are
> visible support a tabindex.

Yes.  I think this comes under the "Have a solution for specifying 
focusability and navigation order, and be consistent with HTML" item in 
http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Commitments. 
We don't have anyone signed up for it yet though.

I don't think it would be much work to add tabindex="" to the spec. 
There is also focus() and blur() on HTMLElement that we would probably 
also want to support.  I wonder what would make the most sense out of

   (a) moving the tabIndex, focus and blur interface members up to
       Element so that SVG would get them for free,

   (b) asking Ian to split out these three members into a separate
       interfaces so that we could say for example

         SVGElement implements FocusControl;

       in our IDL, or

   (c) just duplicating those three interface members on SVGElement.
Received on Sunday, 29 July 2012 22:56:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 29 July 2012 22:56:17 GMT