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

Regarding "editable", does that boil down to text-editable? If that is the case, could we combine this with the hinting we use for `:focus-visible`, which in practice is equivalent to "does this show a virtual keyboard if a physical keyboard is not present"? Could we have a primitive for _that_ concept (which is very close to `inputmode`), instead of making it a separate focus type?

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

Received on Monday, 2 December 2019 19:45:09 UTC