diff options
| author | toyoshim <toyoshim@chromium.org> | 2015-04-02 08:08:47 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-04-02 15:09:14 +0000 |
| commit | 7f47161c5246973e5ed615221e938eab359edfc0 (patch) | |
| tree | c719ea86ef6e1dbf81642acbd6b0fed8c1d4ec76 /components/favicon | |
| parent | f155684660796877ecadb6ac8ca1a7620f483beb (diff) | |
| download | chromium_src-7f47161c5246973e5ed615221e938eab359edfc0.zip chromium_src-7f47161c5246973e5ed615221e938eab359edfc0.tar.gz chromium_src-7f47161c5246973e5ed615221e938eab359edfc0.tar.bz2 | |
Web MIDI: do not manage connection state from embedder side
In the latest spec, each MIDIPort has two separate states. One is
DeviceState, the other is ConnectionState. DeviceState represents the
device being "connected" or "disconnected". ConnectionState represents
the MIDIPort of each MIDIAccess actually being "open" the device or not.
ConnectionState is managed in Blink. So, content implementation do not
have to manage the state. In stead, it should manage actual MIDIAccess
client counts that open the device.
After this change,
MIDI_PORT_DISCONNECTED: means the device is not connected to the system.
MIDI_PORT_CONNECTED: means the device is connected to the system, but
there are no actual clients that open the device.
MIDI_PORT_OPEN: means the device is connected, and at least one client
open the device.
BUG=471793
Review URL: https://codereview.chromium.org/1054913002
Cr-Commit-Position: refs/heads/master@{#323487}
Diffstat (limited to 'components/favicon')
0 files changed, 0 insertions, 0 deletions