WebUSB API #68
Labels
concerns: device independence
Proposal is hardware- or OS-specific, in a way that may risk the device independence of the Web
concerns: privacy
This proposal may cause privacy risk if implemented
concerns: security
This proposal may cause security risk if implemented
from: Google
Proposed, edited, or co-edited by Google.
topic: app-like capabilities
Spec relates to native app style capabilities (e.g. things under the "PWA" or "Fugu" brands)
topic: device apis
Spec relates to device APIs: access to device-specific hardware, sensors, and interfaces
topic: web apis
Spec relates to web APIs (entry points for script)
venue: WICG
Proposal is incubated in the Web Incubator Community Group
(Re-)request for position on an emerging web specification
Information about the spec
Design reviews and vendor positions
Anything else we need to know
WebKit declined to implement several APIs, including WebUSB, due to concerns over fingerprinting:
https://webkit.org/tracking-prevention/
I'm re-requesting WebKit's position on this emerging web specification because of changes we are making to the Chromium implementation related to deprecation of extension background pages in manifest V3. We plan to expose WebUSB to extension service workers as a migration path for extensions that currently access the API from the extension background page.
Chrome Platform Status: https://chromestatus.com/feature/5200265459269632
Explainer: https://github.com/nondebug/webusb/blob/service-worker-explainer/extension-service-worker-explainer.md
Even though Apple is not considering implementing this API, we are still interested in any feedback WebKit can provide on WebUSB and our proposal to integrate with Service Workers.
The text was updated successfully, but these errors were encountered: