That won't work either. <g> is not drawn.
Rich Schwerdtfeger
From: Rik Cabanier <cabanier@gmail.com>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: Erik Dahlström <ed@opera.com>, "www-svg@w3.org"
<www-svg@w3.org>
Date: 04/01/2014 12:33 PM
Subject: Re: [svg2] tabindex and defaults
On Tue, Apr 1, 2014 at 7:20 AM, Richard Schwerdtfeger <schwer@us.ibm.com>
wrote:
Rich Schwerdtfeger
Inactive hide details for Rik Cabanier ---04/01/2014 12:42:02 AM---On
Mon, Mar 31, 2014 at 9:43 PM, Cameron McCormack <cam@mcc.Rik Cabanier
---04/01/2014 12:42:02 AM---On Mon, Mar 31, 2014 at 9:43 PM, Cameron
McCormack <cam@mcc.id.au> wrote: > Rik Cabanier:
From: Rik Cabanier <cabanier@gmail.com>
To: Rik Cabanier <cabanier@gmail.com>, Richard
Schwerdtfeger/Austin/IBM@IBMUS, Erik Dahlström <ed@opera.com>, "
www-svg@w3.org" <www-svg@w3.org>
Date: 04/01/2014 12:42 AM
Subject: Re: [svg2] tabindex and defaults
Hi Rik,
I don't believe we made a formal decision on that.
I did not put tabindex on all SVG elements. Unlike HTML, SVG puts a lot
of their content attributes as DOM elements that are inside the "body" of
an SVG document. Some examples are <title>, <desc>, and <glyph>. Why
would we put tabindex on these elements? What should happen when we put a
tabindex="0" on a <desc>?
That is indeed odd.
Maybe you can say that tabIndex is allowed on all elements, but it only has
an effect on elements that are drawn?
This is what we did in the Blending spec, see the "Applies to" section
here: http://dev.w3.org/fxtf/compositing-1/#mix-blend-mode
