Building an independent web browsers. It's technically feasible and could cost 50-70 millions per year. In comparison, the national space agency costs 7-8 billions and the European union planned 300 millions in digital architecture over the next years.

The Europe rely currently heavily on US technologies, even Firefox is in the US.

Servo is an example of web browser built with 5 engineers, funded by a small company and individual donations.

The core challenge isn’t technical; it’s institutional. It can work though: CERN, European Space Agency, the Internet Engineering Task Force.

Success here would demonstrate that democratic societies can coordinate effectively on complex technical infrastructure and pass the first hurdle. Failure would reveal institutional gaps that need addressing before attempting more ambitious digital sovereignty goals.

Inconsistencies spotted. The URL scheme are hidden or displayed without clear rules

Baseline acts as a flag that tells this feature is supported across browsers.

But there is a few critics:

• Baseline doesn’t take all the browsers they need to support into account
• The safest Baseline stage — Baseline Widely Available — doesn’t cover old enough browser versions, which they still support
• Baseline says nothing about whether a web feature comes with accessibility challenges or no
• Baseline doesn’t tell web developers if it is OK to use a feature that’s not Baseline yet, perhaps as a progressive enhancement, or by using a polyfill.

Here are the definition of a traffic light-style:

• Not Baseline, if a feature is not yet supported on Chrome (desktop and Android), Safari (macOS and iOS), Edge, Firefox (desktop and Android)
• Baseline Newly Available, if it’s supported on the above browsers
• Baseline Widely Available, if it’s been supported on the above browsers for more than 2.5 years

Perfecting baseline: accessibility, flag progressive enhancement, polyfills and best practices; extend browsers and browsers versions to allow configure which (other) browsers should be taken into account.

A new API that aims to improve the history API

The browser behavior in quirk mode.

How to do X in the browser dev tools.

A chromium-based privacy focused browser.

It's similar to LibreWolf for Firefox, but for Chrome.

(via https://korben.info/beachpatrol-cli-automatisation-navigateur-web.html)

It just feels like we have a dozen Band-Aids wrapped around a problem that used to be solved.

I totally agree.

Minecraft running in the browser with web assembly.

Add direct content with designMode = 'on'

A lightweight browser of automation.

It integrates well with Puppeteer or Playwright.

What whis means is that it is possible to open arbitrary applications on your system through a bookmarklet while sending data extracted and preprocessed from the current page by custom JavaScript to that application with the click of a button.

How to create a new URL scheme (such as org-protocol://)

what is really neat here is that with a .desktop file and a bookmarklet, you can send Web data directly from the browser to any local application!

How do we get to a world where our GUIs are as powerful and extensible as our CLIs? When I click Open in Emacs on my bookmark toolbar, and Emacs opens to the code I had open in my browser, I feel like I get a little glimpse of that world that could be.

So it's similar to user agents, do the same thing without standard. What could go wrong? Well the same as User Agents.