New issue
Advanced search Search tips

Issue 727819 link

Starred by 4 users
Status: Available
Owner: ----
Cc:
reillyg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

USB configuration and interface names unpopulated

Project Member Reported by reillyg@chromium.org, May 30 2017 
Chrome Version: 60.0.3107.4
OS: Linux, Chrome OS, macOS and Windows

What steps will reproduce the problem?
(1) Connect USB device which specifies strings on its configurations or interfaces.
(2) Examine the USBDevice object available to web content with permission to access the device.

What is the expected result?
The USBConfiguration.configurationName and USBAlternateInterface.interfaceName fields should be populated with the values from the device.

What happens instead?
The fields are always undefined.

The reason for this is that there is no code in the USB service to collect string IDs from the device's configuration and interface descriptors and query the device for these strings when populating the device info.
Project Member

Comment 1 by sheriffbot@chromium.org, May 31 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Comment 2 by reillyg@chromium.org, Jun 13 2018

Components: -IO>USB Blink>USB
Status: Available (was: Untriaged)
►

Sign in to add a comment