- From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
- Date: Sun, 07 Feb 2016 22:35:25 +0000
- To: public-secondscreen@w3.org
I think we should add `presentation` only if it is used by some UA. At the moment, I don't think there is a need for it and it would be a no-op permission. I'm not sure it is worth it. Regarding `midi`, it was added becaus of `sysex` being linked to a permission (at least in Chrome) and the design of midi is to _request_ midi access. As a consequence, for completeness, instead of having a `midi-sysex` permission, we decided to have a design closer to the Midi API: there is a `midi` permission for which some boolean (like `sysex`) can be passed. Note that Chromium design is changing to allow `midi` to become a real permission. I do not know if Chrome will use it as a real permission but other content embedders (ie. Chromium-based projects like Opera) might have a midi permission. -- GitHub Notification of comment by mounirlamouri Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/255#issuecomment-181135403 using your GitHub account
Received on Sunday, 7 February 2016 22:35:27 UTC