Re: [w3c/webcomponents] Focus delegation from shadow host should not behave like sequential focus navigation (#830)

The disconnect here is that it's highly desirable for JS API `element.focus()` to have interoperable behavior across browsers yet what's being proposed and what Chrome implements can't be.

Also, I'm not certain that using the keyboard-based sequential focus navigation order for when a host element is clicked makes much sense. If the user is clicking somewhere a more sensible thing for the component might be to select the nearest element there is to where the user clicked so perhaps some kind of an event-based focus delegation is needed anyway. In the case where keyboard is used to move focus, however, it obviously makes sense that `tabIndex` order is used.

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