MIDIAccess and MIDIPort statechange_event#14034
Merged
Conversation
Contributor
teoli2003
approved these changes
Mar 18, 2022
Contributor
teoli2003
left a comment
There was a problem hiding this comment.
👍
Doing 2 at once is perfectly fine!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Firstly apologies for doing two at once, but they were so closely related (same event type) and the changes touched all the same pages apart from the event pages themselves it seemed worth it (and still not a big pr)
This changes MIDIAccess.onstatechange to MIDIAccess.statechange_event & MIDIPort.onstatechange to MIDIPort.statechange_event using new template. API landing plus other API pages & interface pages updated to reflect
Related issues
Tracking mdn/browser-compat-data#14578
Also part of #12792
Metadata