1795025 - Enable dom.webmidi.enabled everywhere

Status: RESOLVED FIXED

(Core :: DOM: Device Interfaces, task)

Comment 1

[Bobby Holley (:bholley)]

Attachment: Bug 1795025 - Remove early-beta gate from WebMIDI.

This reverts bug 1765894.

Comment 2

[Bobby Holley (:bholley)]

https://treeherder.mozilla.org/jobs?repo=try&revision=bc0ded2ae537ba57546863280c44541a28065776

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d728a4555222
Remove early-beta gate from WebMIDI. r=gsvelto

Comment 4

[Iulian Moraru]

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

Comment 5

[Hamish Willee]

FF108 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/22111

It would be useful for those docs to be able to link to Firefox documentation on the site permission plugin - something showing how to add, view and disable the plugins. Who is responsible for creating that (i.e. can I have an ETA)?

Comment 6

[Bobby Holley (:bholley)]

There's a rough draft of a SUMO page here: https://support.mozilla.org/en-US/kb/site-permission-addons

Somebody will do a copy-edit pass next week. We're also planning to publish a blog post when 108 hits release.

Comment 7

[Bobby Holley (:bholley)]

Release Note Request (optional, but appreciated)
[Affects Firefox for Android]: No
[Suggested wording]: Firefox now supports the WebMIDI API along with a new experimental mechanism for controlling access to dangerous capabilities.
[Links (documentation, blog post, etc)]: See above

Comment 8

[Hamish Willee]

Bobby, I assume this release note request is not to the MDN docs team?
FYI The MDN release note for this is here. It does not mention that the mechanism is experimental. If that is important I'd expect the information to be in the site-permission-plugin page.

Comment 9

[Bobby Holley (:bholley)]

(In reply to Hamish Willee from comment #8)

Bobby, I assume this release note request is not to the MDN docs team?

I intended it to be for the product release notes — I'm not sure how those relate to the ones on MDN.

FYI The MDN release note for this is here.

Thanks. I might propose rewording the relnote slightly as follows:

The WebMIDI API is now available in secure contexts. Calls to navigator.requestMIDIAccess() will prompt users with active MIDI devices to install a Site Permission Add-On, which is required to enable the API.

Does that seem reasonable? I think linking Site Permission Add-On to the SUMO page, as you do now, should give people enough context if they want to learn more, and that there's no need to send them to this bug.

It does not mention that the mechanism is experimental.

The "experimental" just means that we want to see how well the Site Permission Add-On mechanism works for WebMIDI before we'd consider using it for anything else. This isn't something that users need to worry about.

Comment 10

[Hamish Willee]

Thanks @Bobby. I updated it in https://github.com/mdn/content/pull/22591 to match your suggestion. The original missed the nuance that you get the prompt to install the site permission add on if you have active MIDI devices - not just "attempt to use the API".

I intended it to be for the product release notes — I'm not sure how those relate to the ones on MDN.

They don't relate in any way. Other than perhaps if we see a comment for the product release notes we might "liberate" it for the MDN notes.

"Yes" to all the rest. Very reasonable.