- From: 河内 隆仁 <kochi@google.com>
- Date: Wed, 21 Jan 2015 16:40:57 +0900
- To: public-webapps <public-webapps@w3.org>
- Message-ID: <CADP2=hpd3ehog2v=z1ZdwF7wUCQrQvRu46OoMYyaopuupBu39g@mail.gmail.com>
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
Received on Wednesday, 21 January 2015 07:41:44 UTC