







This archive was generated by hypermail 3.0.0: Thursday, 13 July 2023 18:34:06 UTC
Relative popularity of browsers from Brian Behlendorf on 1994-08-27 (www-talk@w3.org from August 1994)
This archive was generated by hypermail 3.0.0: Tuesday, 27 October 2026 23:17:49 UTC
[httpRange-14] Resolved from Roy T. Fielding on 2005-06-19 (www-tag@w3.org from June 2005)
This archive was generated by hypermail 3.0.0: Thursday, 13 July 2023 17:54:21 UTC
WebView topics from TPAC & upcomming meetings. from Niklas Merz on 2026-11-02 (public-webview@w3.org from November 2026)
This archive was generated by hypermail 3.0.0: Monday, 2 November 2026 15:41:55 UTC
Advance notice: Work in progress on Web Extensions Working Group Charter from Coralie Mercier on 2025-08-07 (public-new-work@w3.org from August 2025)
This archive was generated by hypermail 3.0.0: Thursday, 7 August 2025 13:30:09 UTC
Forget the Fate of Chrome, Focus on the Fate of the Browser
In debating what undoubtedly won't happen, we're looking past some key things that are -- and might...
Our commitment to a more capable web
Since the beginning of Chrome we have worked to provide a solid foundation for modern web applications. Those capabilities have enabled new...

Chrome Users Beware: Manifest V3 is Deceitful and Threatening
Like FLoC and Privacy Sandbox before it, Google Chrome’s Manifest V3 is another example of the inherent conflict of interest that comes from Google controlling both the dominant web browser and one

New Custom Handlers component for Chrome – make everything intensely
The HTML Standard section on Custom Handlers describes the procedure to register custom protocol handlers for URLs with specific schemes. When a URL is followed, the protocol dictates which part of the system handles it by consulting registries. In some cases, handlers may fall to the OS level and and launch a desktop application (eg. mailto:// may launch a native application) or, the browser may redirect the request to a different HTTP(S) URL (eg. mailto:// can go to gmail).
Review | Goodbye, Chrome: Google’s Web browser has become spy software
Our latest privacy experiment found Chrome ushered more than 11,000 tracker cookies into our browser — in a single week.

webmcp is the new web intents ... maybe
One day the web will have a federated way to link to functionality. I swear we will. For those who know me, you can tell that I’ve been thinking about Web Intents again… a lot. If you don’t know me, Web Intents was a 2012 attempt to give the web a vocabulary for “I want to do X, what site can help me?”. Share, edit, pick, save-for-later, buy. And a way for sites to ask for a link to a site that matched their intent. It was basically Android Intents for the web. It got pulled. I’ve written about what happened to Web Intents and again when I was reinventing Web Intents.

Shayan on Twitter / X
I just tried the Dia browser for a few minutes.I'm sorry, but this is most likely ngmi.It's basically Chrome, with an AI chat built in that could've been a Chrome extension.I don't see much of a value prop here, and don't understand why this couldn't have been added to Arc.— Shayan (@ImSh4yy) April 8, 2025
Previous release notes - Chrome Enterprise and Education Help
Note: For information about the current Chrome version and targeted releases, see Chrome Enterprise release notes.

MKBHD reviewed our Arc browser... (CEO reacts)
Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API. We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent. Full details: github.com/mozilla/standards-positions/i…
Prompt API · Issue #1213 · mozilla/standards-positions
github.com