New issue
Advanced search Search tips

Issue 805302 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

WebUSB issue with chrome browser on Windows

Reported by himanshu...@gmail.com, Jan 24 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
1. Connect QL-580N, HP Laserjet P2014 usb printer to Windows(8.1x64 & 10x64) machine
2. Call webUSB  requestDevice() method to access the device in our html page.

In Chrome OS, Mac OSX Yosemite(10.10.5), Sierra(10.12.6) : we are able to see devices listed in chrome dialog and we were able to successfully redirect to our website.

However on Chrome browser on Windows 10x64, Win 8.1x64 : We are not able to see the devices in chrome dialog when we follow the same steps 

What is the expected behavior?
We should be able to see devices listed in chrome USB dialog and should able to redirect to our website in Windows using Chrome browser (same behavior is observed in MAC and Chrome OS)

What went wrong?
Not able to see the devices in chrome dialog in Windows Machines when we try to request access to the device using WebUSB APIs.

I have attached screenshot showing Brother QL-580N listed in device manager in Win8.1 but not  shown on chrome dialog.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 63.0.3239.132  Channel: stable
OS Version: 6.3
Flash Version:
 
win8.1_webusb.PNG
72.1 KB View Download
Status: WontFix (was: Unconfirmed)
This is working as intended. Windows requires a specific device driver, winusb.sys, to be loaded in order for a device to be accessed by a user application like Chrome. Since a USB printer driver seems to be associated with this device instead Chrome cannot connect to it.

It may be possible to construct an INF file that matches the device and loads the WinUSB driver instead.

Sign in to add a comment