Re: [w3c/webcomponents] Mechanism for setting the tabindex focus flag without sprouting tabindex attribute? (#762) from TAMURA, Kent on 2020-03-09 (public-webapps-github@w3.org from March 2020)

From: TAMURA, Kent <notifications@github.com>
Date: Sun, 08 Mar 2020 22:52:57 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/762/596343552@github.com>

@othermaciej 
> I guess you could have voice focus for a voice-only device,

Yes, I supposed such devices which probably don't exist today.

@alice 
> I think the critical concept (other than &lt;select>, which IMO is an outlier) is whether you primarily interact with something via the keyboard - i.e. whether you can type into it.

I agree that &lt;select> is an outlier.  I checked macOS native behavior, not Safari behavior, and found that `NSPopupButton` and widgets like listbox are not tabbable by default.

So, how about `text-control` (behavior like &lt;textarea>) and `control` (behavior like &lt;button>)?  They don't match to the current Safari behavior perfectly, but it should be easy for developers to understand.


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

Received on Monday, 9 March 2020 05:53:09 UTC