Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762)

I don't understand why we need four categories. The previous proposals had three. Punting the "accepts text input" thing to a separate property should collapse two of them, leaving us with two instead of three. We'd have `focusable` and `accepts-text-input` booleans, where the combo of `focusable` being true and `accepts-text-input` being false would be invalid. 

Compared to the two booleans, I think it's simpler to have a single tri-state: `text-input-control`, `control`, `non-control`. Or something.

It seems like you are suggesting that neither the two booleans nor the tri-state adequately cover the possibilities, but I don't understand what is missing. I guess "programmatically focusable" but please make the case for that separately. Seems like that got lost from the conversation after your comment.

-- 
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/762#issuecomment-596361286