-
Notifications
You must be signed in to change notification settings - Fork 21
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
WebUSB API #68
Comments
Thanks @nondebug! We will take a look and get back to you as soon as we can. |
It takes some indirection to tell from the Mozilla standards position issue, but Mozilla has judged this API "harmful", primarily for security reasons. |
We have previously stated privacy concerns, thus the |
Two questions for the WebKit team on whether there are changes that could be made to this API that would affect your position:
|
Maybe we need separate issues for WebUSB for the web vs WebUSB for extensions. It is indeed possible we might endorse this standards proposal in extensions even if not on websites. I took this issue to be about WebUSB in general, and it’s fair that we should get our position on the record on that. |
Thanks, I've filed a separate issue for the extension behavior. |
(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:/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: