[Bug 17417] Define a security model for requesting access to the MIDIAccess interface

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17417

--- Comment #19 from Marcos Caceres <w3c@marcosc.com> ---
(In reply to comment #18)
> Really - I see the potential risks of exposing MIDI; in fact, I've detailed
> them personally in the specification.  At the same time, in the balance with
> user experience - I do not see the need to throw a dialog up in the user's
> face every time they want to use a MIDI controller.  If all I have attached
> to my machine is a keyboard input device, I should be able to say once "yes
> it's cool, don't ask me again" and that should be compliant.

I agree. 

Regarding outputs: Ideally, for system default output (if it can be determined
by the UA) you should not have to ask for permission. It's not really that
different to using <audio autoplay>.

I still think we need to have a bigger discussion about folding MIDIAccess into
a single naviagator.midi. I think it would simplify the API.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 8 January 2013 19:57:17 UTC