Skip to content
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

Feature request. On device webpage support. #228

Open
oiaohm opened this issue Dec 31, 2022 · 0 comments
Open

Feature request. On device webpage support. #228

oiaohm opened this issue Dec 31, 2022 · 0 comments

Comments

@oiaohm
Copy link

oiaohm commented Dec 31, 2022

https://developer.chrome.com/articles/usb/

Buy a USB device.
Plug it into your computer. A notification appears right away, with the right website to go to for this device.
Click the notification. The website is there and ready to use!
Click to connect and a USB device chooser shows up in Chrome where you can pick your device.

Lets think about this workflow little more carefully. You buy device to take it home you plug it in and you get notification about website and you have no internet now how are you going to configure device to use device. Yes the ready to use here presumed working internet connection that is something you should not presume.

Lets say the device has usb storage. There could be a local webpage on device. Now problem how to write URL for web-browser to use the saved webpage on the USB device because the storage of the USB device can be mounted in different locations.

Think about this the webusb information that used to make notification may want to be able to provide ondevice and internet URL for the configuration web page.

I see this as possible coming a generic USB IPP everywhere printing like solution for device configuration. Install less device configuration. The catch is for this to be good install less device configuration just need functional path to work without internet.

This requires 2 things really.

  1. Notification from device being able to have more than 1 URL with user interface that users can understand.
  2. Local URL that able to correctly point to where the local webpage is even if the storage of device is mounted in different location.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant