You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#5050 has implemented ledger-support and thus closed #4060 via #4593. Superseded legacy-issue #717 was closed, too.
Despite the above, this issue here (USB for Extensions) should stay open and WebUSB implementations should be tracked (and even pushed, e.g. via super-bounties on more general bounty-systems, like e.g. https://www.bountysource.com.
We're very interested to see this happen as it would enable us to use WebUSB for the Hangouts Meet speakermic to use together with a Hotrod / CfM running in kiosk mode.
via U2F
Unverified/unconfirmed statement from Chrome project:
This is working as intended. There is currently no clean way of determining an appropriate origin of an extension for the purposes of populating clientData in the U2F protocol. Thus U2F support is limited to web pages.
re #4060 (was #717)
Important
#5050 has implemented ledger-support and thus closed #4060 via #4593. Superseded legacy-issue #717 was closed, too.
Despite the above, this issue here (USB for Extensions) should stay open and WebUSB implementations should be tracked (and even pushed, e.g. via super-bounties on more general bounty-systems, like e.g. https://www.bountysource.com.
via WebUSB
From #4060 (comment))
From https://bugs.chromium.org/p/chromium/issues/detail?id=770896
via U2F
Unverified/unconfirmed statement from Chrome project:
https://bugs.chromium.org/p/chromium/issues/detail?id=823736#c4
Requirements
A patch for the Chrome Browser is created, which fulfills the requirements of the Chrome Team.
The patch must be accepted and applied to the public Chrome Browser.
The text was updated successfully, but these errors were encountered: