[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 #18 from Chris Wilson <cwilso@gmail.com> ---
Grr.  tab-sended accidentally.

> It would have to be sysex - there's no "write access", other than access to
> output ports.  And you could selectively enable sysex port-by-port.  That
> would be marginally acceptable (there are still a lot of devices that use
> sysex heavily for normal operatio
n - for example, the standardized MIDI Machine Control messages
(start/stop/ffw/rewind) are actually sysex messages.  I've been talking to
Incident about the GTar; it, like some other devices, uses sysex for normal
communication.

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.

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

Received on Tuesday, 8 January 2013 17:56:59 UTC