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

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

Chris Lilley <chris@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chris@w3.org

--- Comment #16 from Chris Lilley <chris@w3.org> ---
(In reply to comment #12)
> This level of tweakiness is exactly what I'm worried about.  I don't think
> any sane user will walk through the list of their available MIDI ports and
> carefully select which they're comfortable "sharing" with a web application
> - they'll either say OK or not OK.  And even that, I'd like to minimize as
> much as possible

In general I agree, but I can think of one case where a user might want to have
more fine-grained control. Suppose they are happy to share their input devices
(keyboards, pads etc) and the output devices that can be played (including bank
switch etc) *except* for a device that can be written to destructively (e.g.
can have new patches or samples uploaded, loosing the previously stored ones).

But maybe that is better addressed as write access or disabling sysex rather
than port-by-port.

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

Received on Tuesday, 8 January 2013 17:03:29 UTC