-
Notifications
You must be signed in to change notification settings - Fork 15.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(serial): allow Bluetooth ports to be requested by service class ID #41638
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the GN checks are failing, eg:
https://app.circleci.com/pipelines/github/electron/electron/79480/workflows/73955dd2-f239-4a89-b9e7-527b90a9ac22/jobs/1689290
446bb97
to
60d1de8
Compare
@jkleinsc fixed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
Release Notes Persisted
|
I have automatically backported this PR to "30-x-y", please check out #41734 |
I have automatically backported this PR to "29-x-y", please check out #41735 |
Description of Change
Refs CL:4522192.
In #38465 we added a parameter to
ElectronSerialDelegate::RunChooser
to account for upstream changes but never actually implemented the feature the parameter was added to support. This PR adds support for Bluetooth ports being requested by service class ID, thereby bringing our WebSerial implementation into alignment with the current state of the web platform api. Now, users can do e.g:Checklist
npm test
passesRelease Notes
Notes: Added support for Bluetooth ports being requested by service class ID in
navigator.serial
.