Actually, per https://www.chromium.org/blink/launching-features/#:~:text=Changes%20which%20extend%20an%20already%20exposed%20API%20to%20additional%20platforms this doesn't need approval since it already shipped on other platforms. Rubberstamp LGTM1+LGTM2+LGTM3.
On Wed, Mar 25, 2026 at 4:07 PM Philip Jägenstedt <[email protected]> wrote: > Hi, > > I see that there are existing tests in > https://wpt.fyi/results/serial?label=experimental&label=master&aligned, > but only for things that don't require actually creating a device. > > Do at least these tests also pass on Android? > > Is any work happening to make Serial testable in WPT in general? Something > along the lines of > https://web-platform-tests.org/writing-tests/testdriver.html#bluetooth > should work. > > Best regards, > Philip > > On Tue, Mar 24, 2026 at 8:23 PM Chromestatus < > [email protected]> wrote: > >> *Contact emails* >> [email protected], [email protected] >> >> *Explainer* >> *No information provided* >> >> *Specification* >> *No information provided* >> >> *Summary* >> The Web Serial API provides an interface for connecting to serial >> devices, either through a serial port on the user’s system or removable USB >> and Bluetooth devices that emulate a serial port. Now it is supported on >> Android. Users, especially in the educational, hobbyist and industrial >> sectors, connect peripheral devices to their computers that require custom >> software to control. For example, robotics are often used to teach computer >> programming and electronics in schools. This requires software which can >> upload code to a robot and/or control it remotely. In an industrial or >> hobbyist setting a piece of equipment such as a mill, laser cutter or 3D >> printer is controlled by a program running on a connected computer. These >> devices are often controlled by small microcontrollers via a serial >> connection. Documentation: https://web.dev/serial/ Specification: >> https://wicg.github.io/serial/ >> >> *Blink component* >> Blink>Serial >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ESerial%22> >> >> *Web Feature ID* >> serial <https://webstatus.dev/features/serial> >> >> *Motivation* >> *No information provided* >> >> *Initial public proposal* >> *No information provided* >> >> *TAG review* >> *No information provided* >> >> *TAG review status* >> Issues addressed >> >> *Goals for experimentation* >> None >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: No signal >> >> *WebKit*: No signal >> >> *Web developers*: No signals >> >> *Other signals*: >> >> *WebView application risks* >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> *No information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> No >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> No >> >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> WebSerialWiredDevicesAndroid >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://g-issues.chromium.org/issues/365514951 >> >> *Launch bug* >> https://launch.corp.google.com/launch/4387322 >> >> *Estimated milestones* >> Shipping on Android 148 >> >> *Anticipated spec changes* >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> *No information provided* >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/6043992171085824?gate=5862339666640896 >> >> *Links to previous Intent discussions* >> Intent to Ship: >> https://groups.google.com/a/chromium.org/g/blink-dev/c/yGhvQ6mEmcY/m/xr-aYJ-_AQAJ >> >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69c2e4a0.050a0220.38bee9.0000.GAE%40google.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69c2e4a0.050a0220.38bee9.0000.GAE%40google.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYd2CVPYCX_Jr9MxPS0rgDErFTYW98bbZwOB3WeVQ4yw4Q%40mail.gmail.com.
