Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762) from Maciej Stachowiak on 2019-12-02 (public-webapps-github@w3.org from December 2019)

From: Maciej Stachowiak <notifications@github.com>
Date: Sun, 01 Dec 2019 23:48:56 -0800
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/762/560274987@github.com>

I think "non-keyboardable" might be more clear than "non-editable". But that's still kind of weird since the other types of controls often do handle some keyboard input, even if it's only return or space. "simple-control" also seems good.

One point I am confused about: `control` was described in https://github.com/w3c/webcomponents/issues/762#issuecomment-557488222 as a Safari-specific distinction, but per https://github.com/w3c/webcomponents/issues/762#issuecomment-484461545 , it seems like Chrome would care about this distinction too, at least on macOS.

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

Received on Monday, 2 December 2019 07:48:58 UTC