Web MIDI: do not manage connection state from embedder side

content/renderer/media/midi_message_filter_unittest.cc

Index: content/renderer/media/midi_message_filter_unittest.cc
diff --git a/content/renderer/media/midi_message_filter_unittest.cc b/content/renderer/media/midi_message_filter_unittest.cc
index 5ac0d4ef903e3bb1bec46ccc4b33870036b71c53..b20ebe2f8b13ae3e357c5e2631eef6c5310ef182 100644
--- a/content/renderer/media/midi_message_filter_unittest.cc
+++ b/content/renderer/media/midi_message_filter_unittest.cc
@@ -19,7 +19,11 @@ TEST(MidiMessageFilterTest, CastMidiPortState) {
       MidiMessageFilter::ToBlinkState(media::MIDI_PORT_DISCONNECTED));
   EXPECT_EQ(BlinkState::MIDIPortStateConnected,
       MidiMessageFilter::ToBlinkState(media::MIDI_PORT_CONNECTED));
-  EXPECT_EQ(BlinkState::MIDIPortStateOpened,
+  // Web MIDI API manages DeviceState and ConnectionState separately.
+  // "open", "pending", or "closed" are managed separately for ConnectionState
+  // by Blink per MIDIAccess instance. So, MIDI_PORT_OPENED in content can be
+  // converted to MIDIPortStateConnected.
+  EXPECT_EQ(BlinkState::MIDIPortStateConnected,
       MidiMessageFilter::ToBlinkState(media::MIDI_PORT_OPENED));
 
   // Check if we do not have any unknown MidiPortState that is added later.