W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2015

RE: Better focus support for Shadow DOM

From: Domenic Denicola <d@domenic.me>
Date: Wed, 21 Jan 2015 21:38:46 +0000
To: Takayoshi Kochi (河内 隆仁) <kochi@google.com>, public-webapps <public-webapps@w3.org>
Message-ID: <CY1PR0501MB13693FC2F0C27D3FD45D835EDF480@CY1PR0501MB1369.namprd05.prod.outlook.com>
Thanks Takoyoshi! This new version looks great to me. It would allow people to create custom elements with the same focus capabilities as native elements, including both the simple cases (like <custom-a>) and the more complicated ones with a shadow DOM (like <custom-input type="date">). Very exciting stuff!

I hope others are as enthused as I am :)

From: Takayoshi Kochi (河内 隆仁) [mailto:kochi@google.com]
Sent: Wednesday, January 21, 2015 02:41
To: public-webapps
Subject: Re: Better focus support for Shadow DOM

Hi,

After conversation with Domenic Denicola, I changed the title and the whole story of
solving this issue, though the result is not quite different.  Instead of adding "delegatesFocus"
property, we added "isTabStop()" to expose "tab focusable flag" explained in HTML5 spec.

https://docs.google.com/document/d/1k93Ez6yNSyWQDtGjdJJqTBPmljk9l2WS3JTe5OHHB50/edit?usp=sharing


Any comments/suggestions welcome.

On Wed, Jan 14, 2015 at 2:27 PM, Takayoshi Kochi (河内 隆仁) <kochi@google.com<mailto:kochi@google.com>> wrote:
Hi,

For shadow DOMs which has multiple focusable fields under the host,
the current behavior of tab navigation order gets somewhat weird
when you want to specify tabindex explicitly.

This is the doc to introduce a new attribute "delegatesFocus" to resolve the issue.
https://docs.google.com/document/d/1k93Ez6yNSyWQDtGjdJJqTBPmljk9l2WS3JTe5OHHB50/edit?usp=sharing


Any comments are welcome!
--
Takayoshi Kochi



--
Takayoshi Kochi
Received on Wednesday, 21 January 2015 21:39:17 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:25 UTC