if there's some distinction, that stuff should NOT go to private network access, this could be good.

Private Network Access from the browser? What could possibly go wrong?

Another horrendous proposal by Google. Again.

Isn't Mozilla part of the W3C? When are they going to do something and stop this dreadful specification?

If they will do nothing then I will see them implement this garbage in Firefox soon.

This the reaction to (understandable) community complaints that new browser security improvements make it hard to access local resources. (And complaints that browsers making access to local stuff hard is all a big plot by Google to push people towards using cloud stuff and away from privacy-friendly self-hosting)

Skimming the first few paragraphs, private network access has always been possible. This makes it opt in.

It has always been possible. We have a web app that depends on it being possible so that you can interact with barcode printers and pan/tilt cameras. We have a service clients can install that runs on localhost and allows the web client to interact with hardware.

Can you elaborate on exactly what's horrendous/dreadful about it, rather than who submitted it?