Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774)

> if the shadow host has -1 tab index, any node in a shadow root is skipped, as far as I can read.

I want to stress that the semantics described by @hayatoito is what we believe is the right model. This should not be about `delegatesFocus`, this is about `tabindex`. It is also not about -1 or 0, it is about the possibility of using any other value. If you make this about `delegatesFocus`, it will become really easy for anyone to create a component without `delegatesFocus` flag for its shadow, and any arbitrary tabindex value that will disrupt the page where this component is used. E.g.:

```html
<template>
     <input tabindex="1" />
</template>
```

That should never disrupt the page, no matter what, it is bound to whatever tabindex value its host has, independently of the `delegatesFocus`, otherwise authors can bypass what the consumer of the component is attempting to define. This matches the semantics of the native components.

-- 
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/774#issuecomment-440901622