- From: Michael Kleber via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Oct 2023 15:17:08 +0000
- To: public-patcg@w3.org
We've gotten some pushback about this. Do we have a position on whether it's sufficient to reveal a "this API is not available" kind of signal as long as there are lots of _other_ reasons for an API's unavailability, _aside from_ the user opting out? This seems analogous to e.g. probes for device capabilities. "No you can't have gyroscope sensor access, either because the user said No or because there just is no gyroscope." -- GitHub Notification of comment by michaelkleber Please view or discuss this issue at https://github.com/patcg/docs-and-reports/pull/50#issuecomment-1781334931 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 October 2023 15:17:10 UTC