- From: John Wilander via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Nov 2023 22:54:15 +0000
- To: public-patcg@w3.org
> We've gotten some pushback about this. What is the pushback? I'd like to understand the tradeoff. > 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." I don't think it's analogous. As we've talked about in PATCG meetings, these features are not for users but for site owners and advertisers. Hence, the incentives to push/harass users about their choices are very different than when a function intended for the user is turned off. -- GitHub Notification of comment by johnwilander Please view or discuss this issue at https://github.com/patcg/docs-and-reports/issues/49#issuecomment-1793213564 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 November 2023 22:54:17 UTC