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

Re: tabindex

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 15 Aug 2014 21:27:15 -0700
Message-ID: <CAAWBYDBWMNMc8f92QVRNydB4oaedCCMoU7tqkcyz7fU+moGpFg@mail.gmail.com>
To: Rik Cabanier <cabanier@gmail.com>
Cc: Cameron McCormack <cam@mcc.id.au>, Richard Schwerdtfeger <schwer@us.ibm.com>, SVG WG <public-svg-wg@w3.org>, SVG public list <www-svg@w3.org>
On Fri, Aug 15, 2014 at 8:44 PM, Rik Cabanier <cabanier@gmail.com> wrote:
> On Fri, Aug 15, 2014 at 5:20 PM, Cameron McCormack <cam@mcc.id.au> wrote:
>> Richard Schwerdtfeger wrote:
>>> I just updated the spec. to place tabindex on all elements. This is
>>> where browser implementations are going.
>>
>> Yes I think that's what we want, as HTML also allows tabindex="" to be set
>> on any element (and the DOM property tabIndex is also available on any
>> element).
>>
>> There are two possible futures:
>>
>> (a) we go ahead with my SVG DOM proposals, in which case all SVG elements
>> will end up inheriting from the HTMLElement interface and gain the tabIndex
>> IDL attribute from there
>>
>> (b) we don't go ahead with those proposals, in which case a tabIndex IDL
>> attribute should live on SVGElement
>>
>> Either way, the content attribute tabindex="" is allowed on all elements.
>
> Even on elements that don't display such as defs, lineargradient, symbol,
> etc?

<link>, <meta>, etc all accept tabindex in HTML. They get skipped due
to not being rendered, of course.

~TJ
Received on Saturday, 16 August 2014 04:28:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:19 UTC