Make MIDIMessageEventInit data and MIDIConnectionEventInit port explicitly nullable #257
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.
#252 made MIDIMessageEvent data and MIDIConnectionEvent port nullable.
Based on this comment: #233 (comment) I didn't make the init dictionary members nullable.
However, Chromium currently has these dictionary members nullable:
https://crsrc.org/c/third_party/blink/renderer/modules/webmidi/midi_connection_event_init.idl;l=11
https://crsrc.org/c/third_party/blink/renderer/modules/webmidi/midi_message_event_init.idl;l=11
And Firefox has port nullable (but not data):
https://searchfox.org/mozilla-central/source/dom/webidl/MIDIConnectionEvent.webidl#23
https://searchfox.org/mozilla-central/source/dom/webidl/MIDIMessageEvent.webidl#24
Since the intent was to codify the existing Chromium behavior, I think this means that we should make them both nullable.
This actually does make a difference, since testing in Chromium we get the current behavior:
But after aligning the IDL with the current spec we get the following:
@padenot especially, what do you think?