Chrome 127 shipped with system-level notification controls that bypass Windows’ own Focus Assist settings on certain builds. Most users never noticed. That’s the point.
Browsers have been creeping toward OS-level authority for years, but the pace has shifted. What used to be incremental - offline storage here, camera access there - is now structural. Push notifications, background sync, file system access, Bluetooth, USB, serial ports, GPU compute via WebGPU. The browser now touches almost everything the operating system used to exclusively mediate.
This Isn’t Accidental
Google’s incentive to expand Chrome’s surface area is obvious: the more the web can do natively, the less leverage Microsoft and Apple have over application distribution. Every new Web API that lands in Chrome is a small vote against the App Store and the Microsoft Store. Progressive Web Apps were supposed to be the endgame for this strategy, and they mostly flopped on mobile - but on desktop, the story is different. Electron-based apps are gradually being replaced by browser-based equivalents that don’t even bother pretending to be native. Figma runs in a tab. Notion runs in a tab. Linear runs in a tab.
Microsoft didn’t resist this; they leaned into it. Edge is now the runtime for a growing number of internal enterprise tools, and WebView2 - essentially a sandboxed Edge instance - ships as part of Windows 11 itself. So the browser isn’t competing with the OS. On Windows, it is part of the OS, whether Microsoft frames it that way or not.
The Permission Layer Is the Power
The thing that made operating systems powerful wasn’t the UI chrome or the file manager. It was arbitration - the OS decided what software could access what hardware. Browsers are now that arbitration layer for an expanding category of resources, and they make those decisions through their own permission models, not the system’s.
This matters because browser vendors answer to their own update cadences and their own policy teams. When Chrome decides that certain notification behaviors are acceptable, that decision lands silently on over three billion devices. No OS vendor signed off on it.
The Part Nobody Wants to Say Out Loud
For most users, the browser being the OS is fine, maybe even preferable. Sandboxing is better, updates are automatic, nothing requires admin rights. The concern isn’t usability - it’s accountability. Operating system vendors are subject to antitrust scrutiny, app store review processes, accessibility regulations, and in some jurisdictions, interoperability mandates.
Browsers are getting there, slowly. But they’re accumulating OS-level power on a timeline that regulation hasn’t caught up to yet.