Closed martinthomson closed 7 months ago
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."
@michaelkleber Seeing that you're noting some change on whether we all agree on this I've marked it as needs work and as a candidate for an agenda item in a meeting. If that makes sense to you can you open an issue in meetings?
Let's see if we can resolve it in discussion in #49 — maybe agenda space won't be needed.
For avoidance of doubt: as I said in https://github.com/patcg/docs-and-reports/issues/49#issuecomment-1802485425, Martin's change has resolved my previously-raised concern.
For framing any discussion we have regarding #49.
Closes #49.