Rich Schwerdtfeger
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>?
Rich
On Mon, Mar 31, 2014 at 9:43 PM, Cameron McCormack <cam@mcc.id.au> wrote:
Rik Cabanier:
> A difference with the HTML spec is that tabIndex is allowed on any
element.
Hmm, did we not decide to allow tabindex="" on every element in SVG?
Is the question what value SVGElement.tabIndex should have on elements
that we’ve said the tabindex="" attribute doesn’t apply to?
If we are indeed saying that tabindex="" is only available on some
elements, then perhaps the IDL attribute should be on the interfaces
that correspond to the elements where we’re allowing it.
But as I say, I think we should allow tabindex="" on any element. I
don’t know why this should be any different from HTML.
OK, the HTML recommends that only a set of elements has behavior when
tabindex is missing:
http://www.w3.org/html/wg/drafts/html/master/editing.html#the-tabindex-attribute
.There is no MUST .
Still different than treating is as 0 though.
