[w3ctag/design-reviews] Bluetooth RFCOMM in Web Serial API (Issue #854)

こんにちは TAG-さん!

I'm requesting a TAG review of Bluetooth RFCOMM in Web Serial API.

The Bluetooth RFCOMM (Radio frequency communication) protocol provides emulated RS-232 serial ports. This feature would enable applications to make connections to RFCOMM services on paired Bluetooth Classic devices using the Web Serial API.

  - Explainer: https://github.com/WICG/serial/blob/main/EXPLAINER_BLUETOOTH.md
  - Specification URL: https://wicg.github.io/serial/
  - Tests: In progress
  - User research: N/A
  - Security and Privacy self-review: https://github.com/WICG/serial/blob/main/security-privacy-questionnaire-bluetooth-rfcomm.md
  - GitHub repo (if you prefer feedback filed there): File feedback on this issue
  - Primary contacts (and their relationship to the specification):
      - Matt Reynolds (@nondebug, Google Chrome)
  - Organization(s)/project(s) driving the specification: Google Chrome
  - Key pieces of existing multi-stakeholder review or discussion of this specification:
      - Gecko: Negative signals (https://github.com/mozilla/standards-positions/issues/336 https://github.com/mozilla/standards-positions/issues/687)
      - WebKit: Negative signals (https://webkit.org/tracking-prevention/ https://github.com/WebKit/standards-positions/issues/199)
  - External status/issue trackers for this specification (publicly visible, e.g. Chrome Status): [Chrome Status: Web Serial support for Bluetooth RFCOMM services](https://chromestatus.com/feature/5686596809523200)

Further details:

  - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
  - Relevant time constraints or deadlines: We expect to start an experiment with this feature in Chrome 116
  - The group where the work on this specification is currently being done: WICG
  - The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): Device & Sensors Working Group
  - Major unresolved issues with or opposition to this specification:
      - Apple and Mozilla are both opposed to Web Serial API
  - This work is being funded by: Google Chrome

You should also know that...

The feature can be enabled in Chrome 116 with the flag chrome://enable-bluetooth-spp-in-serial-api.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

  💬 leave review feedback as a **comment in this issue** and @-notify @nondebug



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/854
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/854@github.com>