1796191 - Separate midi and midi-sysex permissions

Status: RESOLVED FIXED

(Core :: DOM: Device Interfaces, defect, P3)

Description

[Bobby Holley (:bholley)]

In our first iteration of the addon-gating experiment, there was an explicit sign-up step by the site. Since we figured that anybody going through this flow would want to grant themselves sysex, we decided to avoid making it a parameter to simplify the experience. Now that we've switched towards automatic generation, that's no longer a concern.

On the UX side, we see both midi and midi-sysex as dangerous and requiring heightened consent (as opposed to Chrome, which grants midi to all sits without any consent at all). So we're going to use an equally-scary dialog whether sysex is requested or not.

However, I do think there's some value in segregating the permissions anyway. First, it follows the principle of least privilege (why give sites firmware access when they didn't even request it?). Second, it could reduce webcompat risk, since a site designed for Chrome that does not request sysex might theoretically break if those additional unexpected APIs are present when running in Firefox.

Comment 1

[Nicolas Chevobbe [:nchevobbe][PTO - back October 26]]

Attachment: Bug 1796191 - Separate midi and midi-sysex permissions. r=gsvelto.

Depends on D159480

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d1e86449623f
Separate midi and midi-sysex permissions. r=gsvelto.

Comment 3

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/d1e86449623f