By that logic, every website should bundle their own web browser. They don't. Browsers are consistent enough, especially when you limit your web browsers to only those that OSes provide as web view components.
Bundling your dependencies is in fact something applications like to do though. The question becomes whether your browser/runtime is the layer you stop including deps or the os native apis which that browser is built on top is. When you get to physical products the OS is absolutely part of the dependencies you want to control and deploy, even if it largely exists to run a single application.
Safari and Edge scare the user about pointer lock control, which makes it annoying/impossible to build nice 3D games or visualizations in Tauri. Every on click event is met with a huge, scary browser-native alert. Chrome doesn't do that.
That's just one of dozens of browser inconsistencies we've recently dealt with. It's just the most egregious.
Safari and Edge aren't that interesting, since Tauri uses the OS's native web view, not Safari or Edge. Are you saying that the web view also scares the user about pointer lock control?
Yes. The OS's native web view uses the same rendering/JS engines as the OS's preferred browser choice. This is why native web views are inconsistent, and in this case, crippled.