W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Better focus support for Shadow DOM

From: 河内 隆仁 <kochi@google.com>
Date: Wed, 3 Jun 2015 16:47:51 +0900
Message-ID: <CADP2=hoHouct+x+-Aye-2xs=YU-1VerPijy4w0Ehta3Jt0NpAA@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>
Hi,

(cross-posting mostly the same content to blink-dev@chromium.org, sorry for
duplication if you encounter this twice)

With much feedback from many people, I've updated the design doc.
https://docs.google.com/document/d/1k93Ez6yNSyWQDtGjdJJqTBPmljk9l2WS3JTe5OHHB50/edit?usp=sharing
Thanks all who have shared thoughts and experience with me.

The biggest change is that "tabStop" property on Element moved to
ShadowRoot, as "delegatesFocus".

After implementing the spec on Blink, I noticed that even tabStop property
is
on every Element, it has effect only on shadow hosts, which is very
confusing.
So delegatesFocus should make more clear sense on shadow hosts.

With the new spec, delegatesFocus can be specified via ShadowRootInit
dictionary,
which is a parameter to createShadowRoot().

I'll start making changes in Blink immediately.

For reference, I copied a snapshot of old doc (Mar. 19):
https://docs.google.com/document/d/1wFXrPYmoqb8-b-rfZdmcVfZt09NaTFyOLvGztdlIPxE/edit#

Any comment is welcome.

On Thu, Jan 22, 2015 at 6:38 AM, Domenic Denicola <d@domenic.me> wrote:

>  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>
> 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
>



-- 
Takayoshi Kochi
Received on Wednesday, 3 June 2015 07:48:41 UTC

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