libwdi VS standards-positions

They probably use WCID, which is a mechanism for devices to tell Windows that they are compatible with the generic WinUSB driver. Zadig is useful for older versions of windows, non-WCID devices, and when you want to override that auto-specified driver.

Here's more information from the author of Zadig: https://github.com/pbatard/libwdi/wiki/WCID-Devices

If you do that'll bring you here where you'll find everything you ever wanted to know about WCID.

Using this config files from zadig's github page, it (in my case) got all the correct settings from the start and all I need to do is click replace driver. Place the zadig.ini files in the same directory as your zadig.exe. You might have to choose the correct device.

USB descriptors are supported only up to 8.1 according to your link. And libwdi/zadig is useful links for me, thank you very much! I'll be used ones in my other projects. But I don't need to new USB driver in Windows due to I'll get much more problems with put all together in LabView. I want to use standard WIndows USB-Serial that always present and directly supported via VISA. The NI-VISA isn't using specific protocols for USB. The VISA is just an intermediate level for most of the serial protocols in the NI ecosystem. I'm operating low-level USB packets, commands, responses in the same manner as in C for example but from LabView. But I have to generate the specific INF file which needs for recognition of VISA for each one of the specific instances with a unique USB PID/UID. The problem is mandatory signing such INF files in Windows10 and I'm looking for any way to avoid this.

You can read through the conversations to understand more of the context

https://github.com/mozilla/standards-positions/issues/100#is...

https://github.com/mozilla/standards-positions/issues/95#iss...

https://github.com/mozilla/standards-positions/issues/336

The main struggle is around giving informed consent that explains the risks. Understandably, browsers don't want to ship a "Set my printer on fire" button.

You can check why Mozilla and Apple have opted to not support this.

https://github.com/mozilla/standards-positions/issues/154

https://github.com/WebKit/standards-positions/issues/28

Neither Mozilla or Webkit are satisfied that the proposal is safe by default, and contains footguns for the user that can be pretty destructive.

FWIW Mozilla updated their position on Web Serial API to "neutral" and clarified that they might be okay with enabling the API with an add-on.

https://mozilla.github.io/standards-positions/#webserial

Allowing serial but not HID would be really strange. With HID you get standard identifiers that let you filter out devices that are too dangerous for the web. With serial you get nothing. Even if you know a device is dangerous, there's no way to protect users from it.

Hasn't FireFox been dragging their asses on @scope? https://github.com/mozilla/standards-positions/issues/472

It took years to just convince them of the need for it. And I'm not sure anyone got convinced vs Chrome had already shipped it and Safari has it planned so they caved in.

Hard to believe FireFox used to be a leader of the modern web.

As mentioned by others, OK idea, but not a fan that this isn't standardized. After a quick search+peruse, these seem to indicate that it's not around the corner either. Happy (/hope) to be corrected.

https://github.com/whatwg/html/issues/4180

https://github.com/mozilla/standards-positions/issues/990

Mozilla's position on these specs is nicely outlined publicly and transparently as part of their standards-positions project: https://github.com/mozilla/standards-positions/issues/100

I'm kinda glad it's not implemented in my browser, to be honest, because the whole thing seems like a security nightmare.

It's a shame it impacts some hobby usecases, but I don't think this outweighs the reasoning set out on the GitHub issue.

This should have big warnings on it. Some of these are not web standards; they are features implemented unilaterally by Google in Blink that have been explicitly rejected by both Mozilla and Apple on privacy and security grounds.

Take Web Bluetooth, for example:

Mozilla:

> This model is unsustainable and presents a significant risk to users and their devices.

— https://mozilla.github.io/standards-positions/#web-bluetooth

Apple:

> Here are some examples of features we have decided to not yet implement due to fingerprinting, security, and other concerns, and where we do not yet see a path to resolving those concerns

— https://webkit.org/tracking-prevention/

This is Microsoft’s Embrace, Extend, and Extinguish bullshit applied to the web platform by Google. Google keeps implementing these things despite all other major rendering engines rejecting them, convinces people that they are part of the web, resulting in sites like this, then people start asking why Firefox and Safari are “missing functionality”. These are not part of the web platform, they are Google APIs that have been explicitly rejected.

Is BLE a PWA requirement? I think they explained their position pretty well here, regardless of whether I agree:

https://github.com/mozilla/standards-positions/issues/95#iss...

I took a glance at Can I Use what the difference between the last public release of Firefox and Chrome is [1] and they don't really have that big of a difference in the eyes of normal use-cases? Some of these aren't implemented purely because of privacy reasons, the proposals aren't finished yet or complexity [2].

Why would Firefox need to change to Chromium engine? The only websites I notice that don't work with Firefox is because of user-agent targetting or just putting 5-second time-outs in Youtube code on non-chrome webbrowsers [3].

Can you give some examples of websites not working on Firefox?

[1] https://caniuse.com/?compare=chrome+120%2Cfirefox+121&compar...

[2] https://mozilla.github.io/standards-positions/

[3] https://www.neowin.net/news/youtube-seemingly-intentionally-...