What I haven’t seen in the discussions here so far is that Chromium is the web engine that most mobile apps are built on (you don’t build your own special web client to access the server for your app, you just use an existing system for that). Also it’s the engine used for most web apps for embedded/standalone/IoT devices. The Electron application framework has Chromium embedded in it for web access - every Electron app uses Chromium. If your climate control device has a little touchscreen and smart features it’s probably using a web app that runs in an embedded instance of Chromium. Basically any device that has a GUI and links to cloud services is probably doing the same thing.
Bluntly, when it comes to client-side access to web services, Chromium matters more than Firefox, and anything that happens with it is far more impactful because it applies to a broader context than just people using Chrome for regular web browsing.
What I haven’t seen in the discussions here so far is that Chromium is the web engine that most mobile apps are built on (you don’t build your own special web client to access the server for your app, you just use an existing system for that). Also it’s the engine used for most web apps for embedded/standalone/IoT devices. The Electron application framework has Chromium embedded in it for web access - every Electron app uses Chromium. If your climate control device has a little touchscreen and smart features it’s probably using a web app that runs in an embedded instance of Chromium. Basically any device that has a GUI and links to cloud services is probably doing the same thing.
Bluntly, when it comes to client-side access to web services, Chromium matters more than Firefox, and anything that happens with it is far more impactful because it applies to a broader context than just people using Chrome for regular web browsing.