- From: Rossen Atanassov <notifications@github.com>
- Date: Mon, 04 Apr 2022 10:04:59 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 4 April 2022 17:05:11 UTC
@domenic, we had [another round of discussions with TAG](https://cryptpad.w3ctag.org/code/#/2/code/view/4HndN5ayJ8-2PpuDydAwoOBEpFyfGigMPpff5vCRTH8/) today and our consensus is still wanting to see [detectability of the proposed feature](https://www.w3.org/TR/design-principles/#feature-detect). We want to close the review with this last issue addressed. (assuming detectability is provided) Another question I have is whether you considered exposing finer granularity of UI detectability? In the case a picker is supported, that picker can be UI implemented by the browser vs the OS native picker. This type of distinction will be just as important when component implementers are making the decision to show native vs theirs. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/688#issuecomment-1087799665 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/688/1087799665@github.com>
Received on Monday, 4 April 2022 17:05:11 UTC