Port the chrome.usb API to the USB Mojo service |
||||||
Issue descriptionTo allow the USB service to be moved into a separate device service process all consumers of the //device/usb C++ API must be moved to the //device/usb/public/interfaces Mojo API. This bug tracks porting the implementation of the chrome.usb Extensions API located in //extensions/browser/api/usb.
,
Jun 7 2017
,
Nov 7 2017
,
Nov 7
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 7
Donna, will you be working on this next?
,
Nov 9
Reilly, yes, I'd like to take this. I'm working on mojom interface converting under //chrome/browser/devtools/usb(the logic is a bit complicated for me), will get start on //extensions next.
,
Dec 10
,
Today
(2 hours ago)
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/72336f11501d5e76aa1f4314fcd482c475dce953 commit 72336f11501d5e76aa1f4314fcd482c475dce953 Author: Donna Wu <donna.wu@intel.com> Date: Wed Jan 23 06:25:11 2019 Use device::mojom::UsbDeviceInfo in UsbDevicePermission. Bug: 716628 Change-Id: I0eb098a88533effec8b67b499fe98f8b39b20fc3 Reviewed-on: https://chromium-review.googlesource.com/c/1420274 Commit-Queue: Donna Wu <donna.wu@intel.com> Reviewed-by: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#625114} |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by reillyg@chromium.org
, Apr 28 2017