[w3c/permissions] Mechanism for permission feature-detection? (#134)

Is it possible that an application may want to have different behavior depending on whether a permission is supported by the browser or not?  Should there perhaps be some mechanism for feature-detecting unsupported permissions separately from denied permissions?

I'm just worried about developers relying on UserAgent checks (which then cause interoperability and forwards compatibility issues) when what they really want is a permission feature detect.

/cc @jyasskin where this came up in [the intent-to-ship for web bluetooth](https://groups.google.com/a/chromium.org/d/msg/blink-dev/Ono3RWkejAA/37k_TWevAgAJ).

-- 
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/permissions/issues/134