- From: Justin Fagnani <notifications@github.com>
- Date: Wed, 28 Aug 2019 09:15:23 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 28 August 2019 16:15:45 UTC
I haven't used `delegatesFocus` yet. Maybe @azakus, who's working on the material design components, can comment from actual usage. But reading the details (thanks for the very clear explanation @rakina), it doesn't sound to me like any choice is going to be all that great. We have to choose either the first sequential or first clickable focusable element - and in either case we're only inferring what the component author wants in the face of no explicit `onfocus` event handler. I honestly find either choice strange in its own way. `tabindex-1` could be interpreted to mean "only focus this element explicitly" and yet the proposed change would add a new want to focus it without actually clicking it or calling `focus()`. The thing I find particularly strange about the proposed change is that we'd be picking the _first_ click-focusable element, ie sequentially., where order doesn't matter otherwise. At least with Chrome's current behavior the author already expects that tabindex ordering and tree-order matter. All that said, I don't feel particularly strongly here. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/830#issuecomment-525816361
Received on Wednesday, 28 August 2019 16:15:45 UTC