Chrome 130 supports connection events with Bluetooth RFCOMM serial ports #25234
Conversation
This file contains 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
github-actions
bot
added
data:api
caugner
changed the title
caugner
changed the title
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
Co-authored-by: Claas Augner <495429+caugner@users.noreply.github.com>
|
WFM; thanks @caugner! |
chrisdavidmills
deleted the
web-serial-connected-disconnected-event-rfcomm-support
branch
Merged
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.
…onected events
Summary
Chrome 130 supports the
SerialPort.connectedattribute, a boolean that reports whether a serial port is logically connected. This property is already represented in BCD.However, another part of this work item is that the
SerialPortconnectanddisconnectevents were previously only fired by physical/wired serial ports. With this change, wireless Bluetooth RFCOMM serial ports also fire these events when they connect and disconnect.This PR adds a data point to cover this new wireless support for the events. Note that it looks like this change is a result of a spec change (I'm not sure which exact spec change, but WICG/serial#189 mentions adding Bluetooth support) rather than Chrome previously having partial support. As a result, I've added a sub-data point rather than another support item in the same support array.
Test results and supporting details
See https://chromestatus.com/feature/5118102654418944
Related issues