# Chromium

Chromium is an open-source browser project focused on a safer, faster, and more stable way to experience the web.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Google Is Testing a Search Bar That Works Outside Chrome

DevFeed: [Google Is Testing a Search Bar That Works Outside Chrome](<https://devfeed.tech/articles/google-is-testing-a-search-bar-that-works-outside-chrome-9270.md>)

Original publisher: [Read original article](<https://webdesignerdepot.com/google-is-quietly-testing-a-search-bar-that-works-outside-chrome/>)

Author: Simon Sterne

Published: 2026-09-10T16:00:00Z

Content type: article

Language: en

Sources: [Web Designer Depot](<https://devfeed.tech/sources/web-designer-depot.md>)

Topics: [Chrome](<https://devfeed.tech/topics/chrome.md>), [Google](<https://devfeed.tech/topics/google.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [ai-search](<https://devfeed.tech/tags/ai-search.md>), [ai-tech](<https://devfeed.tech/tags/ai-tech.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browser-design](<https://devfeed.tech/tags/browser-design.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chrome-canary](<https://devfeed.tech/tags/chrome-canary.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [everywhere-omnibox](<https://devfeed.tech/tags/everywhere-omnibox.md>), [future-of-browsers](<https://devfeed.tech/tags/future-of-browsers.md>), [future-of-search](<https://devfeed.tech/tags/future-of-search.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [gemini-in-chrome](<https://devfeed.tech/tags/gemini-in-chrome.md>), [google](<https://devfeed.tech/tags/google.md>), [google-chrome](<https://devfeed.tech/tags/google-chrome.md>), [google-search](<https://devfeed.tech/tags/google-search.md>), [project-loom](<https://devfeed.tech/tags/project-loom.md>), [search](<https://devfeed.tech/tags/search.md>), [search-technology](<https://devfeed.tech/tags/search-technology.md>), [ui-design](<https://devfeed.tech/tags/ui-design.md>), [ux-design](<https://devfeed.tech/tags/ux-design.md>), [web-browsers](<https://devfeed.tech/tags/web-browsers.md>), [web-design](<https://devfeed.tech/tags/web-design.md>)

### AI overview

Google is testing Project Loom, an experimental floating Search bar that can appear over other Windows apps instead of remaining inside Chrome. The feature is unfinished, with screen sharing, Lens, and AI Mode controls reportedly not yet working.

### Source excerpt

Google is quietly testing a way to bring Search outside Chrome and directly on top of whatever app you're using. It's called Project Loom, and this little floating search box could hint at a much bigger future where Google follows you around your desktop.

## Novel Blue Moon kit targeting Chrome and Windows reflects new reality of AI-driven exploits

DevFeed: [Novel Blue Moon kit targeting Chrome and Windows reflects new reality of AI-driven exploits](<https://devfeed.tech/articles/novel-blue-moon-kit-targeting-chrome-and-windows-reflects-new-reality-of-ai-driven-exploits-8559.md>)

Original publisher: [Read original article](<https://www.theregister.com/research/2026/09/09/novel-blue-moon-kit-targeting-chrome-and-windows-reflects-new-reality-of-ai-driven-exploits/5295399>)

Author: Jessica Lyons

Published: 2026-09-09T22:28:53Z

Content type: news

Language: en

Sources: [www.theregister.com - Articles](<https://devfeed.tech/sources/www-theregister-com-articles.md>)

Topics: [BlueMoon](<https://devfeed.tech/topics/bluemoon.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [cve-2026-85880](<https://devfeed.tech/topics/cve-2026-85880.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [bluemoon](<https://devfeed.tech/tags/bluemoon.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [cve-2026-85880](<https://devfeed.tech/tags/cve-2026-85880.md>), [exploits](<https://devfeed.tech/tags/exploits.md>), [google](<https://devfeed.tech/tags/google.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [proofpoint](<https://devfeed.tech/tags/proofpoint.md>), [research](<https://devfeed.tech/tags/research.md>), [reverse-engineering](<https://devfeed.tech/tags/reverse-engineering.md>), [security](<https://devfeed.tech/tags/security.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Proofpoint reports that multiple espionage clusters used the BlueMoon exploit kit to chain Chromium-based browser flaws with a Windows bug. The article says AI agents may lower the barrier to exploit development, particularly during the window between upstream Chromium patches and downstream stable releases.

### Source excerpt

Mind the patch gap, please and thank you

## Security updates for Wednesday

DevFeed: [Security updates for Wednesday](<https://devfeed.tech/articles/security-updates-for-wednesday-8496.md>)

Original publisher: [Read original article](<https://lwn.net/Articles/1093342/>)

Author: jzb

Published: 2026-09-09T13:04:46Z

Content type: news

Language: en

Sources: [LWN.net](<https://devfeed.tech/sources/lwn-net.md>)

Topics: [Debian](<https://devfeed.tech/topics/debian.md>), [cURL](<https://devfeed.tech/topics/curl.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [systemd](<https://devfeed.tech/topics/systemd.md>), [Terraform](<https://devfeed.tech/topics/terraform.md>), [.NET](<https://devfeed.tech/topics/net.md>)

Tags: [chromium](<https://devfeed.tech/tags/chromium.md>), [cli](<https://devfeed.tech/tags/cli.md>), [debian](<https://devfeed.tech/tags/debian.md>), [google](<https://devfeed.tech/tags/google.md>), [intel](<https://devfeed.tech/tags/intel.md>), [java](<https://devfeed.tech/tags/java.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [python](<https://devfeed.tech/tags/python.md>), [redis](<https://devfeed.tech/tags/redis.md>), [security](<https://devfeed.tech/tags/security.md>), [systemd](<https://devfeed.tech/tags/systemd.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Security updates have been issued across AlmaLinux, Debian, Fedora, Mageia, Red Hat, SUSE, and Ubuntu for a broad set of packages, including kernels, systemd, Chromium, curl, Python, Java, Terraform provider components, and other system and developer tools.

### Source excerpt

Security updates have been issued by AlmaLinux (expat, glib2, microcode_ctl, mrtg, pam, redis, thunderbird, and valkey), Debian (fort-validator, gst-plugins-base1.0, kernel, and slurm-wlm), Fedora (complyctl, libevent, openvpn, and tar), Mageia (dovecot and spice-vdagent), Red Hat (ignition, opentelemetry-collector, and osbuild-composer), SUSE (amazon-ssm-agent, aws-nitro-enclaves-cli, bzip2, cadvisor, chromium, curl, distribution-registry, emacs, freeciv, fuse-overlayfs, gh, google-guest-agent, GraphicsMagick, hauler, insighttoolkit-devel, java-17-openjdk, libidn, libusb-1_0, libvirt, libvncserver, libzypp, zypper, lkl, lxd, multipath-tools, NetworkManager, perl-Net-DNS, perl-URI, python, python-authlib, python-sqlparse, python-tornado, python3, rpcbind, supergfxctl, systemd, terraform-provider-null, ucode-intel, wget, wireshark, and xen), and Ubuntu (curl, ffmpeg, glibc, hsqldb1.8.0, imagemagick, perl, and vim).

## Cypress 16: faster tests, starting with HTTP/2 support

DevFeed: [Cypress 16: faster tests, starting with HTTP/2 support](<https://devfeed.tech/articles/cypress-16-faster-tests-starting-with-http-2-support-12602.md>)

Original publisher: [Read original article](<https://www.cypress.io/blog/cypress-16-faster-tests-starting-with-http2-support/>)

Published: 2026-09-01T17:28:34Z

Content type: release

Language: en

Sources: [Cypress Blog](<https://devfeed.tech/sources/cypress-blog.md>)

Topics: [Cypress](<https://devfeed.tech/topics/cypress.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [Streaming](<https://devfeed.tech/topics/streaming.md>), [Vite](<https://devfeed.tech/topics/vite.md>)

Tags: [chromium](<https://devfeed.tech/tags/chromium.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cypress](<https://devfeed.tech/tags/cypress.md>), [http](<https://devfeed.tech/tags/http.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [tests](<https://devfeed.tech/tags/tests.md>), [vite](<https://devfeed.tech/tags/vite.md>)

### AI overview

Cypress 16 improves end-to-end test performance with HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie and storage commands, and automatic memory management. The release also updates Node.js, Electron, and Chromium versions and removes Cypress.env() as part of its security work.

### Source excerpt

Cypress 16 goes after slow test suites from every angle: HTTP/2 support, zero-delay typing, faster visibility checks, retrying cookie commands, and automatic memory management. Most of it arrives without editing a single test. Here's what changed, why, and how to upgrade.

## Кому верит Яндекс Браузер и как попасть в этот список: запускаем Yandex Browser Root Certificate Program

DevFeed: [Кому верит Яндекс Браузер и как попасть в этот список: запускаем Yandex Browser Root Certificate Program](<https://devfeed.tech/articles/yandex-browser-root-certificate-program-24888.md>)

Original publisher: [Read original article](<https://habr.com/ru/companies/yandex/articles/1075148/>)

Author: Ilya\_Golubtsov (Яндекс)

Published: 2026-08-28T08:00:27Z

Content type: release

Language: ru

Sources: [Яндекс - Как мы делаем Яндекс / Статьи](<https://devfeed.tech/sources/source.md>)

Topics: [browser](<https://devfeed.tech/topics/browser.md>), [яндекс](<https://devfeed.tech/topics/tag-4004cf5948d3.md>), [Certificate Transparency](<https://devfeed.tech/topics/certificate-transparency.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [browser](<https://devfeed.tech/tags/browser.md>), [certificate-transparency](<https://devfeed.tech/tags/certificate-transparency.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [tag-2b4427fb2566](<https://devfeed.tech/tags/tag-2b4427fb2566.md>), [tag-4004cf5948d3](<https://devfeed.tech/tags/tag-4004cf5948d3.md>), [tag-4d5248fd6bfe](<https://devfeed.tech/tags/tag-4d5248fd6bfe.md>), [tag-d8952f30fc4a](<https://devfeed.tech/tags/tag-d8952f30fc4a.md>), [tag-dfac9042ce7b](<https://devfeed.tech/tags/tag-dfac9042ce7b.md>)

### AI overview

Yandex opens the Yandex Browser Root Certificate Program, a public process for adding root certificates to the browser's trust store. The article explains its participation requirements, auditing process, WebPKI controls, and the browser's use of Chromium-derived trust data and separate Certificate Transparency logs.

### Source excerpt

За 15 лет WebPKI -- экосистема доверия между сайтами и пользователями -- сильно выросла. Появились технологии, которые делают это доверие более прозрачным и проверяемым, изменились подходы к управлению, а многие процессы стали автоматическими: выпуск и обновление сертификатов, публичный аудит через Certificate Transparency и другие механизмы. И, конечно, в истории WebPKI были серьёзные инциденты безопасности, которые показали: правила доверия должны быть публичными, прозрачными и проверяемыми. Однако один вопрос не решается автоматически: кому браузер должен доверять и на каких условиях. Каждый вендор определяет это сам. Поэтому мы открываем Yandex Browser Root Certificate Program -- публичную программу добавления корневых сертификатов в хранилище Яндекс Браузера. В ней описаны требования к участникам, аудит и понятная процедура подачи заявки. Под катом рассказываем, какие требования нужно выполнить и как в Браузере устроены WebPKI и связанные с ними контроли безопасности. Читать далее

## Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3

DevFeed: [Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3](<https://devfeed.tech/articles/moving-the-microsoft-edge-extensions-ecosystem-forward-with-manifest-version-3-4251.md>)

Original publisher: [Read original article](<https://blogs.windows.com/msedgedev/2026/08/07/moving-the-microsoft-edge-extensions-ecosystem-forward-with-manifest-version-3/>)

Author: Microsoft Edge Team

Published: 2026-08-07T15:54:07Z

Content type: news

Language: en

Sources: [Microsoft Edge Blog](<https://devfeed.tech/sources/microsoft-edge-blog.md>)

Topics: [Edge](<https://devfeed.tech/topics/edge.md>), [Extension](<https://devfeed.tech/topics/extension.md>), [migration](<https://devfeed.tech/topics/migration.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [chromium](<https://devfeed.tech/tags/chromium.md>), [developer](<https://devfeed.tech/tags/developer.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [edge](<https://devfeed.tech/tags/edge.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-edge](<https://devfeed.tech/tags/microsoft-edge.md>), [migration](<https://devfeed.tech/tags/migration.md>), [security](<https://devfeed.tech/tags/security.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

Microsoft Edge announces the next phase of its transition from Manifest V2 to Manifest V3 for extensions. Consumer migration begins in August 2026 and is expected to finish by the end of 2026, followed by enterprise deprecation in early 2027.

### Source excerpt

Back in 2020, we committed to Manifest Version 3 (MV3) as the future direction of the Chromium extensions platform. Since then, we've worked with developer The post Moving the Microsoft Edge extensions ecosystem forward with Manifest Version 3 appeared first on Microsoft Edge Blog.

## How Yandex explains Android mechanisms in Yandex Browser and the Yandex app

DevFeed: [How Yandex explains Android mechanisms in Yandex Browser and the Yandex app](<https://devfeed.tech/articles/android-24879.md>)

Original publisher: [Read original article](<https://habr.com/ru/companies/yandex/articles/1067964/>)

Author: BarakAdama (Яндекс)

Published: 2026-08-07T13:01:54Z

Content type: opinion

Language: ru

Sources: [Яндекс - Как мы делаем Яндекс / Статьи](<https://devfeed.tech/sources/source.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [tag-2b4427fb2566](<https://devfeed.tech/tags/tag-2b4427fb2566.md>), [tag-4004cf5948d3](<https://devfeed.tech/tags/tag-4004cf5948d3.md>)

### AI overview

This article responds to an earlier analysis of Yandex Browser and the Yandex Android app. It explains that some observed methods, permissions, and network calls are standard Android, Chromium, voice-assistant, or payment-SDK mechanisms, while noting that the original analysis did not specify app versions.

### Source excerpt

На днях на Хабре вышла статья с разбором Яндекс Браузера и приложения Яндекс для Android. Автор сделал несколько выводов о работе приложений на основе анализа кода. Часть наблюдений в статье действительно описывает существующие механизмы, однако их назначение интерпретируется неверно. Во многих случаях речь идёт не о специфике Яндекса, а о стандартных механизмах Android, Chromium, работе современных голосовых помощников или платёжных SDK. При реверс-инжиниринге мобильного приложения очень легко увидеть большое количество подозрительно выглядящих методов, разрешений и сетевых вызовов. Намного сложнее понять, зачем они существуют и как используются на самом деле. Поэтому мы решили разобрать основные тезисы статьи и объяснить, как эти механизмы работают на практике. Сразу оговоримся: автор не указал версии приложений, которые анализировал, поэтому в точности воспроизвести его опыт невозможно. Для разбора мы использовали актуальные версии Яндекс Браузера и приложения Яндекс из Google Play. Все описанные ниже механизмы можно проверить самостоятельно. Читать далее

## Give your eve agent a browser

DevFeed: [Give your eve agent a browser](<https://devfeed.tech/articles/give-your-eve-agent-a-browser-953.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/give-your-eve-agent-a-browser>)

Author: Chris Tate

Published: 2026-08-04T04:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Agent Browser](<https://devfeed.tech/topics/agent-browser.md>), [Extension](<https://devfeed.tech/topics/extension.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [browser](<https://devfeed.tech/topics/browser.md>), [selectors](<https://devfeed.tech/topics/selectors.md>), [Template](<https://devfeed.tech/topics/template.md>), [Forms](<https://devfeed.tech/topics/forms.md>), [Network](<https://devfeed.tech/topics/network.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [auth](<https://devfeed.tech/tags/auth.md>), [browser](<https://devfeed.tech/tags/browser.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [extension](<https://devfeed.tech/tags/extension.md>), [forms](<https://devfeed.tech/tags/forms.md>), [network](<https://devfeed.tech/tags/network.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [selectors](<https://devfeed.tech/tags/selectors.md>), [storage](<https://devfeed.tech/tags/storage.md>), [tools](<https://devfeed.tech/tags/tools.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Vercel announces an eve extension that adds agent-browser capabilities to eve agents. It enables browser navigation, content inspection, clicking, form filling, screenshots, and console and network inspection inside the agent sandbox, with selector-based interaction and controls for isolation, domains, credentials, approvals, and tool access.

### Source excerpt

Your eve agent can now navigate the web like a human with agent-browser. The @agent-browser/eve extension gives any eve agent a full set of browser tools: navigate pages, read content, click, fill forms, take screenshots, and inspect console and network activity. Everything runs inside the agent's sandbox. Install the extension: Then mount it under agent/extensions/: Your agent gets namespaced tools like browser__navigate, browser__snapshot, browser__click, browser__fill, and browser__screenshot. Snapshot refs such as [ref=e12] become @e12 selectors, so the agent can inspect a page, then act on exactly what it saw. The extension includes: Sandbox isolation: Chromium and agent-browser run in the eve sandbox, not your app. Pre-install them in your sandbox template so sessions start warm, or let the extension install them on first use. Domain allowlist: Restrict navigation and subresources with allowedDomains, and control output size, screenshot handling, proxy use, and session naming through extension options. Credential protection: Cookie, storage, and saved-auth-state commands are never exposed to the model. Use eve extension overrides to disable tools, require approvals, or add app-specific guarded tools. See a complete Next.js eve app with the extension mounted in the example, or read the documentation to get started. Read more

## The Electron browser is being deprecated in Cypress

DevFeed: [The Electron browser is being deprecated in Cypress](<https://devfeed.tech/articles/the-electron-browser-is-being-deprecated-in-cypress-12615.md>)

Original publisher: [Read original article](<https://www.cypress.io/blog/the-electron-browser-is-being-deprecated-in-cypress/>)

Published: 2026-07-10T15:15:58Z

Content type: article

Language: en

Sources: [Cypress Blog](<https://devfeed.tech/sources/cypress-blog.md>)

Topics: [Cypress](<https://devfeed.tech/topics/cypress.md>), [Electron](<https://devfeed.tech/topics/electron.md>), [Testing](<https://devfeed.tech/topics/testing.md>), [browsers](<https://devfeed.tech/topics/browsers.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [continuous-integration](<https://devfeed.tech/tags/continuous-integration.md>), [cypress](<https://devfeed.tech/tags/cypress.md>), [edge](<https://devfeed.tech/tags/edge.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Cypress is deprecating its bundled Electron browser starting with Cypress 16.0.0 and plans to remove it in a future major version. The article explains that tests can produce inconsistent results in Electron compared with users' installed browsers, and recommends moving local and CI runs to installed browsers such as Chrome for Testing, Chrome, Firefox, or Edge.

### Source excerpt

We're deprecating the Electron browser in Cypress, starting in Cypress 16.0.0, with removal in a future major version. After years of seeing inconsistent results between Electron and the browsers people actually use, we are standardizing on installed browsers for more reliable test results.

## Recent lld/ELF performance improvements

DevFeed: [Recent lld/ELF performance improvements](<https://devfeed.tech/articles/recent-lld-elf-performance-improvements-31121.md>)

Original publisher: [Read original article](<https://maskray.me/blog/2026-04-12-recent-lld-elf-performance-improvements>)

Published: 2026-04-12T07:00:00Z

Content type: article

Language: en

Sources: [MaskRay](<https://devfeed.tech/sources/maskray.md>)

Topics: [LLVM](<https://devfeed.tech/topics/llvm.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [benchmarking](<https://devfeed.tech/topics/benchmarking.md>), [clang](<https://devfeed.tech/topics/clang.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [clang](<https://devfeed.tech/tags/clang.md>), [gc](<https://devfeed.tech/tags/gc.md>), [gdb](<https://devfeed.tech/tags/gdb.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [linker](<https://devfeed.tech/tags/linker.md>), [lld](<https://devfeed.tech/tags/lld.md>), [llvm](<https://devfeed.tech/tags/llvm.md>), [macos](<https://devfeed.tech/tags/macos.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [patches](<https://devfeed.tech/tags/patches.md>), [performance](<https://devfeed.tech/tags/performance.md>)

### AI overview

This article reports LLVM lld/ELF linker performance improvements from parallelizing link phases and reducing task-runtime overhead. Benchmarks show a 1.34x speedup over lld 22.1 for a Release+Asserts clang link and a 1.09x speedup for a Chromium debug link, while mold and wild remain faster in the comparisons described.

### Source excerpt

Updated in 2026-05. Since the LLVM 22 branch was cut, I've landed patches that parallelize more link phases and cut task-runtime overhead. This post compares current main against lld 22.1, mold, and wild. Headline: a Release+Asserts clang --gc-sections link is 1.34x as fast as lld 22.1; Chromium debug with --gdb-index is 1.09x as fast. mold and wild are still ahead -- the last section explains why.

## Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers

DevFeed: [Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers](<https://devfeed.tech/articles/squarespace-web-standards-how-we-helped-bring-html-video-audio-lazy-loading-to-today-s-browsers-30781.md>)

Original publisher: [Read original article](<https://engineering.squarespace.com/blog/2026/squarespace-and-web-standards-how-we-helped-bring-html-video-and-audio-lazy-loading-to-todays-browsers>)

Author: Scott Jehl

Published: 2026-03-30T21:00:00Z

Content type: article

Language: en

Sources: [Squarespace](<https://devfeed.tech/sources/squarespace.md>), [Squarespace Engineering Blog](<https://devfeed.tech/sources/squarespace-engineering-blog.md>)

Topics: [web-standards](<https://devfeed.tech/topics/web-standards.md>), [lazy loading](<https://devfeed.tech/topics/lazy-loading.md>), [HTML](<https://devfeed.tech/topics/html.md>), [Web platform](<https://devfeed.tech/topics/web-platform.md>), [WebKit](<https://devfeed.tech/topics/webkit.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Google Chrome](<https://devfeed.tech/topics/google-chrome.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [html](<https://devfeed.tech/tags/html.md>), [lazy-loading](<https://devfeed.tech/tags/lazy-loading.md>), [standards](<https://devfeed.tech/tags/standards.md>), [web-standards](<https://devfeed.tech/tags/web-standards.md>)

### AI overview

Squarespace engineers describe how they helped add lazy loading for HTML video and audio to the HTML Standard. They contributed proposed implementations for Firefox and WebKit, worked with Chromium developers on a Google Chrome implementation, and added automated testing.

### Source excerpt

At Squarespace, many of our core products are built on web standards, and our engineers are constantly pushing the boundaries of the web's capabilities. Occasionally, those boundaries reveal a limitation: an opportunity for the web's native capabilities to grow. This post is the story of how we found such an opportunity to work with the standards community to improve the web in a way that we - and everyone who uses it - can benefit.

## Bringing Chrome to ARM64 Linux Devices

DevFeed: [Bringing Chrome to ARM64 Linux Devices](<https://devfeed.tech/articles/bringing-chrome-to-arm64-linux-devices-4198.md>)

Original publisher: [Read original article](<https://blog.chromium.org/2026/03/bringing-chrome-to-arm64-linux-devices.html>)

Author: Chromium Blog (noreply@blogger.com)

Published: 2026-03-12T20:01:00Z

Content type: release

Language: en

Sources: [Chromium Blog](<https://devfeed.tech/sources/chromium-blog.md>)

Topics: [Chrome](<https://devfeed.tech/topics/chrome.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Google](<https://devfeed.tech/topics/google.md>), [Extension](<https://devfeed.tech/topics/extension.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Security](<https://devfeed.tech/topics/security.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Malware](<https://devfeed.tech/topics/malware.md>), [passwords](<https://devfeed.tech/topics/passwords.md>), [DGX Spark](<https://devfeed.tech/topics/dgx-spark.md>), [data](<https://devfeed.tech/topics/data.md>), [real-time](<https://devfeed.tech/topics/real-time.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [arm](<https://devfeed.tech/tags/arm.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [data](<https://devfeed.tech/tags/data.md>), [dgx-spark](<https://devfeed.tech/tags/dgx-spark.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [google](<https://devfeed.tech/tags/google.md>), [linux](<https://devfeed.tech/tags/linux.md>), [malware](<https://devfeed.tech/tags/malware.md>), [none](<https://devfeed.tech/tags/none.md>), [passwords](<https://devfeed.tech/tags/passwords.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Google announces the launch of Chrome for ARM64 Linux devices in Q2 2026, extending Chrome's availability across Arm-powered platforms. The release brings Google ecosystem integration, cross-device synchronization, extensions, translation, security protections, password management, and support for DGX Spark users.

### Source excerpt

We're excited to announce that Google will launch Chrome for ARM64 Linux devices in Q2 2026, following the successful expansion of Chrome to Arm-powered macOS devices in 2020 and Arm-powered Windows devices in 2024. Launching Chrome for ARM64 Linux devices allows more users to enjoy the seamless integration of Google's most helpful services into their browser. This move addresses the growing demand for a browsing experience that combines the benefits of the open-source Chromium project with the Google ecosystem of apps and features. This release represents a significant undertaking to ensure that ARM64 Linux users receive the same secure, stable, and rich Chrome experience found on other platforms. Get the best of the Google ecosystem With Chrome, you are able to leverage the full power of the Google ecosystem, providing a more cohesive and feature-rich environment designed for convenience and cross-device continuity. By signing into a Google Account, your bookmarks, browsing history, and open tabs follow you across devices. You can easily access the best extensions the Chrome Web Store has to offer, without needing to use specialized tools or alter developer settings. And you can effortlessly translate webpages with a single click. Use the browser that is secure by design Chrome also offers the added benefit of Google's strongest security protections. Enabling Enhanced Protection in Safe Browsing offers real-time protection against phishing and malware by leveraging AI alongside Google's list of known threats. With the Google Pay integration you can easily and securely manage your payments, using Chrome autofill for an added level of convenience. And the Google Password Manager lets you securely store, generate, and sync complex passwords across all your devices, eliminating the need to memorize multiple logins. It goes beyond simple storage by actively monitoring your credentials for data breaches and providing "Password Checkup" alerts if any of your accounts are

## A Visual Feedback Loop for Electron Apps with Claude Code

DevFeed: [A Visual Feedback Loop for Electron Apps with Claude Code](<https://devfeed.tech/articles/a-visual-feedback-loop-for-electron-apps-with-claude-code-21153.md>)

Original publisher: [Read original article](<https://juri.dev/articles/visual-feedback-loop-electron-apps-claude-code/>)

Published: 2026-03-06T00:00:00Z

Content type: tutorial

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [Electron](<https://devfeed.tech/topics/electron.md>), [Agent Browser](<https://devfeed.tech/topics/agent-browser.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [agent-browser](<https://devfeed.tech/tags/agent-browser.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [devtools](<https://devfeed.tech/tags/devtools.md>), [electron](<https://devfeed.tech/tags/electron.md>), [nx](<https://devfeed.tech/tags/nx.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

This tutorial explains how to give Claude Code visual feedback when building Electron applications. It uses agent-browser and the Chrome DevTools Protocol to connect to a running Electron app, capture screenshots, inspect the DOM, and verify that the rendered interface works. The article covers installing the required tooling, enabling CDP, configuring electron-vite and Nx development scripts, and checking the CDP endpoint.

### Source excerpt

A Visual Feedback Loop for Electron Apps with Claude Code When building Electron apps with an AI coding agent, you run into a fundamental problem: the agent can't see what it's building. It writes code, runs the build, maybe checks the logs, but never actually looks at the rendered UI. If the window is blank or the layout is broken, it has no way to know. I found a way to close that gap using agent-browser and Chrome DevTools Protocol (CDP).

## How fast do browsers correct UTF-16 strings?

DevFeed: [How fast do browsers correct UTF-16 strings?](<https://devfeed.tech/articles/how-fast-do-browsers-correct-utf-16-strings-29392.md>)

Original publisher: [Read original article](<https://lemire.me/blog/2026/02/21/how-fast-do-browsers-correct-utf-16-strings/>)

Author: Daniel Lemire

Published: 2026-02-21T20:07:17Z

Content type: article

Language: en

Sources: [Daniel Lemire](<https://devfeed.tech/sources/daniel-lemire.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Edge](<https://devfeed.tech/topics/edge.md>), [Bun](<https://devfeed.tech/topics/bun.md>)

Tags: [benchmark](<https://devfeed.tech/tags/benchmark.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [bun](<https://devfeed.tech/tags/bun.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [edge](<https://devfeed.tech/tags/edge.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [programming](<https://devfeed.tech/tags/programming.md>)

### AI overview

This article explains how JavaScript represents UTF-16 strings, how invalid surrogate sequences can be repaired with toWellFormed, and how fast the operation runs. A benchmark across browsers and JavaScript runtimes found varied performance; Chromium-based browsers exceeded ten gigabytes per second in the reported test.

### Source excerpt

JavaScript represents strings using Unicode, like most programming languages today. Each character in a JavaScript string is stored using one or two 16-bit words. The following JavaScript code might surprise some programmers because a single character becomes two 16-bit words. > t="🧰" '🧰' > t.length 2 > t[0] '\ud83e' > t[1] '\uddf0' The convention is ... Continue reading How fast do browsers correct UTF-16 strings?

## How we built OWL, the new architecture behind our ChatGPT-based browser, Atlas

DevFeed: [How we built OWL, the new architecture behind our ChatGPT-based browser, Atlas](<https://devfeed.tech/articles/how-we-built-owl-the-new-architecture-behind-our-chatgpt-based-browser-atlas-6321.md>)

Original publisher: [Read original article](<https://openai.com/index/building-chatgpt-atlas>)

Published: 2025-10-30T00:00:00Z

Content type: article

Language: en

Sources: [OpenAI News](<https://devfeed.tech/sources/openai-news.md>)

Topics: [ChatGPT](<https://devfeed.tech/topics/chatgpt.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [agentic browsing](<https://devfeed.tech/topics/agentic-browsing.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [agentic-browsing](<https://devfeed.tech/tags/agentic-browsing.md>), [chatgpt](<https://devfeed.tech/tags/chatgpt.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [core](<https://devfeed.tech/tags/core.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [openai](<https://devfeed.tech/tags/openai.md>), [patches](<https://devfeed.tech/tags/patches.md>), [ui](<https://devfeed.tech/tags/ui.md>), [web-engine](<https://devfeed.tech/tags/web-engine.md>)

### AI overview

OpenAI engineers explain OWL, the architecture behind ChatGPT Atlas. The design decouples the browser application from the Chromium runtime to support fast startup, responsiveness across many tabs, a rebuilt native UI, targeted Chromium patches, and agentic browsing.

### Source excerpt

A deep dive into OWL, the new architecture powering ChatGPT Atlas--decoupling Chromium, enabling fast startup, rich UI, and agentic browsing with ChatGPT.

## Web Standards and the Fall of the House of Iamus

DevFeed: [Web Standards and the Fall of the House of Iamus](<https://devfeed.tech/articles/web-standards-and-the-fall-of-the-house-of-iamus-26559.md>)

Original publisher: [Read original article](<https://infrequently.org/2025/09/standards-and-the-fall-of-iamus/>)

Author: Alex Russell

Published: 2025-09-21T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [web-standards](<https://devfeed.tech/topics/web-standards.md>), [browsers](<https://devfeed.tech/topics/browsers.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [standards](<https://devfeed.tech/tags/standards.md>), [web](<https://devfeed.tech/tags/web.md>), [web-standards](<https://devfeed.tech/tags/web-standards.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

This commentary argues that web standards and Working Groups generally document, refine, and spread designs that have already demonstrated value rather than determining what browsers may ship. It concludes that responsible feature development depends on thoughtful launch processes, not prior consensus.

### Source excerpt

Photo by Photo by Artan Sadiku Commentary about browsers and the features they support is sometimes pejorative towards pre-standardisation features. Given Apple's constriction of Mozilla's revenue stream and its own strategic under-funding of WebKit, this usually takes the form "Chromium just ships whatever it wants." This is true, of course, but not in the way commenters intend; and not only because Blink's rigorous launch process frequently prevents unvalidated designs from shipping. Except for iOS, where Apple attempts to hide its role in undermining the competitive foundation of web standards, every vendor always ships "whatever it wants." That is the point of voluntary standards, and competition is the wind in those sails. Working Groups don't gate what browsers ship, nor do they define what's useful or worthy. There are no seers; no Delphic oracles that fleetingly glimpse a true logos. Working Groups do not invent the future, nor do they hand down revealed truths like prophets of the House of Iamus. In practice, they are thoughtful historians of recent design expeditions, critiquing, tweaking, then spreading the good news of proposals that already work through Web Standards ratified years after features first ship, serving to licence designs liberally to increase their spread. In the end, this is the role of standards and the Working Groups that develop them: to license patents that read on existing designs, reducing risks to implementers who adopt them. Anyone who tries to convince you otherwise, or invites you to try your hand at invention within a chartered Working Group, does not understand what those groups are designed to do. Sadly, this includes some folks who spend a lot of time in them. Contents Terminology Traps Standardisation != Interoperability Standardisation != Responsibility What Working Groups Really Do Chartered Working Groups Are Not Design Venues The Role of Incubation No Prophecies, Only Engineering Complaints about certain engines leading

## Figma rendering: Powered by WebGPU

DevFeed: [Figma rendering: Powered by WebGPU](<https://devfeed.tech/articles/figma-rendering-powered-by-webgpu-9703.md>)

Original publisher: [Read original article](<https://www.figma.com/blog/figma-rendering-powered-by-webgpu/>)

Author: Alex Ringlein; Luke Anderson

Published: 2025-09-18T00:00:00Z

Content type: article

Language: en

Sources: [Figma Blog](<https://devfeed.tech/sources/figma-blog.md>)

Topics: [Figma](<https://devfeed.tech/topics/figma.md>), [webgpu](<https://devfeed.tech/topics/webgpu.md>), [WebGL](<https://devfeed.tech/topics/webgl.md>), [Optimization](<https://devfeed.tech/topics/optimization.md>), [GPU](<https://devfeed.tech/topics/gpu.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [cpu](<https://devfeed.tech/topics/cpu.md>), [shaders](<https://devfeed.tech/topics/shaders.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [compatibility](<https://devfeed.tech/tags/compatibility.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [figma](<https://devfeed.tech/tags/figma.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [graphics](<https://devfeed.tech/tags/graphics.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [performance](<https://devfeed.tech/tags/performance.md>), [shaders](<https://devfeed.tech/tags/shaders.md>), [webgl](<https://devfeed.tech/tags/webgl.md>), [webgpu](<https://devfeed.tech/tags/webgpu.md>)

### AI overview

Figma explains its migration from WebGL to WebGPU to improve rendering performance. The article describes compute shaders, moving work from the CPU to the GPU, reducing reliance on global state, modernizing the rendering interface, and maintaining WebGL compatibility during the rollout.

### Source excerpt

We've updated our renderer to use WebGPU, unlocking new performance optimization opportunities. Here's how we did it.

## Inline Style Exfiltration: leaking data with chained CSS conditionals

DevFeed: [Inline Style Exfiltration: leaking data with chained CSS conditionals](<https://devfeed.tech/articles/inline-style-exfiltration-leaking-data-with-chained-css-conditionals-7683.md>)

Original publisher: [Read original article](<https://portswigger.net/research/inline-style-exfiltration>)

Author: Gareth Heyes

Published: 2025-08-26T12:54:03Z

Content type: article

Language: en

Sources: [PortSwigger Research](<https://devfeed.tech/sources/portswigger-research.md>)

Topics: [CSS](<https://devfeed.tech/topics/css.md>), [browsers](<https://devfeed.tech/topics/browsers.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [selectors](<https://devfeed.tech/topics/selectors.md>)

Tags: [browsers](<https://devfeed.tech/tags/browsers.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [code](<https://devfeed.tech/tags/code.md>), [css](<https://devfeed.tech/tags/css.md>)

### AI overview

The article presents a CSS injection technique that exfiltrates attribute data through inline styles, without selectors or stylesheet imports. It uses CSS conditionals, nested comparisons, and background requests to test possible values, with Burp Suite Custom Actions helping brute-force non-complex data such as user IDs and usernames. The technique reportedly works only in Chromium-based browsers at the time of writing.

### Source excerpt

I discovered how to use CSS to steal attribute data without selectors and stylesheet imports! This means you can now exploit CSS injection via style attributes! Learn how below: Someone asked if you c

## Tiny Agents: an MCP-powered agent in 50 lines of code

DevFeed: [Tiny Agents: an MCP-powered agent in 50 lines of code](<https://devfeed.tech/articles/tiny-agents-an-mcp-powered-agent-in-50-lines-of-code-7514.md>)

Original publisher: [Read original article](<https://huggingface.co/blog/tiny-agents>)

Author: Julien Chaumond

Published: 2025-04-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [Hugging Face - Blog](<https://devfeed.tech/sources/hugging-face-blog.md>)

Topics: [Model Context Protocol (MCP)](<https://devfeed.tech/topics/model-context-protocol-mcp.md>), [AI Development](<https://devfeed.tech/topics/ai-development.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Playwright](<https://devfeed.tech/topics/playwright.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [browser](<https://devfeed.tech/tags/browser.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [hub](<https://devfeed.tech/tags/hub.md>), [inference](<https://devfeed.tech/tags/inference.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llms](<https://devfeed.tech/tags/llms.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

### AI overview

This tutorial explains how MCP exposes tools to LLMs and shows how to build a simple TypeScript agent around an MCP client in about 50 lines of code. The example connects to local filesystem and Playwright MCP servers, enabling file operations and sandboxed Chromium browsing, with configurable model and provider settings.

### Source excerpt

We're on a journey to advance and democratize artificial intelligence through open source and open science.

## Announcing Supporters of Chromium-based Browsers

DevFeed: [Announcing Supporters of Chromium-based Browsers](<https://devfeed.tech/articles/announcing-supporters-of-chromium-based-browsers-4192.md>)

Original publisher: [Read original article](<https://blog.chromium.org/2025/01/announcing-supporters-of-chromium-based.html>)

Author: Chromium Blog (noreply@blogger.com)

Published: 2025-01-09T17:01:00Z

Content type: release

Language: en

Sources: [Chromium Blog](<https://devfeed.tech/sources/chromium-blog.md>)

Topics: [Chromium](<https://devfeed.tech/topics/chromium.md>), [linux foundation](<https://devfeed.tech/topics/linux-foundation.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [Google](<https://devfeed.tech/topics/google.md>)

Tags: [announce](<https://devfeed.tech/tags/announce.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [linux-foundation](<https://devfeed.tech/tags/linux-foundation.md>), [none](<https://devfeed.tech/tags/none.md>), [open-source](<https://devfeed.tech/tags/open-source.md>)

### AI overview

Google announced a partnership with the Linux Foundation and the launch of Supporters of Chromium-based Browsers, a fund intended to support open-source contributions and developers working on the Chromium ecosystem.

### Source excerpt

Since Google announced the Chromium project in 2008, we have been excited to build on the great foundations of open-source web browsers and contribute to the continued development of a rich web platform. Today, Chromium is used by hundreds of different projects globally, including big browsers like Chrome, home electronics from LG, application frameworks like Electron and even custom applications like Bloomberg terminals and SpaceX capsule control software. In 2024, Google made over 100,000 commits to Chromium, accounting for ~94 percent of contributions. While we have no intention of reducing this investment, we continue to welcome others stepping up to invest more. Google also continues to invest heavily in the shared infrastructure of the Open Source project to "keep the lights on", including having thousands of servers endlessly running millions of tests, responding to hundreds of incoming bugs per day, ensuring the important ones get fixed, and constantly investing in code health to keep the whole project maintainable. This work represents hundreds of millions of US dollars in annual investment just for maintenance costs before any new feature, innovation or other business priorities can be addressed. Sustainable funding of critical open source infrastructure remains a hot industry-wide topic of discussion and over the years we've heard from many companies and developers about how critical the Chromium project is to their work. They've also shared how they would like to support the continued health of the project, beyond direct engineering support. Today Google is pleased to announce our partnership with The Linux Foundation and the launch of the Supporters of Chromium-based Browsers. The goal of this initiative is to foster a sustainable environment of open-source contributions towards the health of the Chromium ecosystem and financially support a community of developers who want to contribute to the project, encouraging widespread support and continued techno

## Nuxt 3.15

DevFeed: [Nuxt 3.15](<https://devfeed.tech/articles/nuxt-3-15-3428.md>)

Original publisher: [Read original article](<https://nuxt.com/blog/v3-15>)

Published: 2024-12-24T00:00:00Z

Content type: release

Language: en

Sources: [The Nuxt Blog](<https://devfeed.tech/sources/the-nuxt-blog.md>)

Topics: [Nuxt.js](<https://devfeed.tech/topics/nuxt.md>), [Vite](<https://devfeed.tech/topics/vite.md>), [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [development](<https://devfeed.tech/tags/development.md>), [performance](<https://devfeed.tech/tags/performance.md>), [release](<https://devfeed.tech/tags/release.md>), [vue](<https://devfeed.tech/tags/vue.md>)

### AI overview

Nuxt 3.15 is a release featuring Vite 6, improved integration with Chromium-based browser developer tools, enhanced hot module reloading, navigation-specific execution options, page metadata extraction, app manifest preloading, and bundle optimizations. It also includes changes related to the upcoming Nuxt v4 defaults and provides upgrade guidance.

### Source excerpt

Nuxt 3.15 is out - with Vite 6, better HMR and faster performance

## How to make the iPhone Continuity Camera work properly in Chrome

DevFeed: [How to make the iPhone Continuity Camera work properly in Chrome](<https://devfeed.tech/articles/how-to-make-the-iphone-continuity-camera-work-properly-in-chrome-25270.md>)

Original publisher: [Read original article](<https://kau.sh/blog/iphone-camera-chrome/>)

Author: Kaushik Gopal

Published: 2024-12-12T07:00:00Z

Content type: tutorial

Language: en

Sources: [Kaushik Gopal's Site](<https://devfeed.tech/sources/kaushik-gopal-s-site.md>)

Topics: [iphone](<https://devfeed.tech/topics/iphone.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>), [webcam](<https://devfeed.tech/topics/webcam.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Google Meet](<https://devfeed.tech/topics/google-meet.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [browser](<https://devfeed.tech/topics/browser.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [camera](<https://devfeed.tech/tags/camera.md>), [chrome](<https://devfeed.tech/tags/chrome.md>), [google](<https://devfeed.tech/tags/google.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [macos](<https://devfeed.tech/tags/macos.md>), [webcam](<https://devfeed.tech/tags/webcam.md>)

### AI overview

A practical guide explains how to make an iPhone using Continuity Camera appear as a webcam in Google Meet on Chromium browsers. The phone must be in landscape mode, have its screen off, be locked and motionless, and have an unobstructed camera.

### Source excerpt

I use a pixel as my primary android phone. But as a mobile developer, I also keep an iPhone handy for those times I need to test how an app works on iOS (especially if it's not available on Android1). But my iPhone doesn't sit in a drawer unused. It doubles up as my webcam when not being used as a phone. This is possible because I use macOS for my primary desktop needs, and this wonderful feature it enables called "Continuity Camera". I've removed a webcam from my setup thanks to this, and the camera actually works much better than most webcams out there today. But there's one really annoying thing about this setup. It won't be recognized in Google Meet when using a chromium browser. Searching on Reddit points out that this is a bizzarre known security requirement for chromium browsers alone. Your iPhone needs: to be in landscape mode (so don't have portrait lock on) have the screen turned off to be locked motionless (so won't work if handheld) and have an unobstructed camera wut 😵💫 But works like a charm. So if you run into this issue, fix those things and it'll all work like a charm. thinking about you Flighty. ↩︎

## BenefitsCal's Performance Problems Compared with getcalfresh.org

DevFeed: [BenefitsCal's Performance Problems Compared with getcalfresh.org](<https://devfeed.tech/articles/reckoning-part-2-object-lesson-26545.md>)

Original publisher: [Read original article](<https://infrequently.org/2024/08/object-lesson/>)

Author: Alex Russell

Published: 2024-08-13T00:00:00Z

Content type: article

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [Core Web Vitals](<https://devfeed.tech/topics/core-web-vitals.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [Compression](<https://devfeed.tech/topics/compression.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [caching](<https://devfeed.tech/tags/caching.md>), [compression](<https://devfeed.tech/tags/compression.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [core-web-vitals](<https://devfeed.tech/tags/core-web-vitals.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [web](<https://devfeed.tech/tags/web.md>), [webdev](<https://devfeed.tech/tags/webdev.md>)

### AI overview

The article compares California's BenefitsCal public benefits portal with Code for America's getcalfresh.org. It argues that BenefitsCal delivers a substantially slower experience, with excessive JavaScript, multiple loading screens, and configuration problems, while getcalfresh.org uses a simpler HTML-first architecture and becomes interactive sooner.

### Source excerpt

Other posts in the series: Reckoning: Part 1 -- The Landscape Reckoning: Part 3 -- Caprock Reckoning: Part 4 -- The Way Out Contents The Golden Wait The Truth Is In The Trace Zip It Near Peers Blimey JavaScript Masshattery Maryland Enters The Chat Chattanooga Chug Chug SNAP? In Jersey? Fuhgeddaboudit Hoosier Hospitality Deep Breaths The Golden Wait BenefitsCal is the state of California's recently developed portal for families that need to access SNAP benefits (née "food stamps"):1 BenefitsCal loading on a low-end device over a 9Mbps link with 170ms RTT latency via WebPageTest.org Code for America's getcalfresh.org performs substantially the same function, providing a cleaner, faster, and easier-to-use alternative to California county and state benefits applications systems: getcalfresh.org loading under the same conditions The like-for-like, same-state comparison getcalfresh.org provides is unique. Few public sector services in the US have competing interfaces, and only Code for America was motivated to build one for SNAP applications. getcalfresh.org finishes in 1/3 the time, becoming interactive not long after the BenefitsCal loading screen appears. WebPageTest.org timelines document a painful progression. Users can begin to interact with getcalfresh.org before the first (of three) BenefitsCal loading screens finish (scroll right to advance): & & Google's Core Web Vitals data backs up test bench assessments. Real-world users are having a challenging time accessing the site: BenefitsCal is a poor experience on real phones. But wait! There's more. It's even worse than it looks. The multi-loading-screen structure of BenefitsCal fakes out Chrome's heuristic for when to record Largest Contentful Paint. On low-end devices, BenefitsCal appears to almost load at the 22 second mark, only to put up a second loading screen shortly after. Because this takes so long, Chromium's heuristics for Largest Contentful Paint are thrown off, incorrectly reporting the end of the first loa

## How JavaScript-First Frontend Practices Struggled with the Mobile Web

DevFeed: [How JavaScript-First Frontend Practices Struggled with the Mobile Web](<https://devfeed.tech/articles/reckoning-part-1-the-landscape-26546.md>)

Original publisher: [Read original article](<https://infrequently.org/2024/08/the-landscape/>)

Author: Alex Russell

Published: 2024-08-12T00:00:00Z

Content type: opinion

Language: en

Sources: [Alex Russell](<https://devfeed.tech/sources/alex-russell.md>)

Topics: [Front end](<https://devfeed.tech/topics/frontend.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Web Development](<https://devfeed.tech/topics/web-development.md>), [Chrome](<https://devfeed.tech/topics/chrome.md>), [WebView](<https://devfeed.tech/topics/webview.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [performance](<https://devfeed.tech/tags/performance.md>), [webdev](<https://devfeed.tech/tags/webdev.md>), [webview](<https://devfeed.tech/tags/webview.md>)

### AI overview

This first part of a four-part investigation examines how JavaScript-first frontend culture developed alongside the mobile web. It describes browser development for Android, the challenges of Chromium's memory-hungry multi-process sandboxing, and the introduction of PWAs and Push Notifications, then argues that desktop-oriented JavaScript frameworks brought unnecessary bloat to mobile-first projects.

### Source excerpt

Instead of an omnibus mega-post, this investigation into JavaScript-first frontend culture and how it broke US public services has been released in four parts. Other posts in the series: Reckoning: Part 2 -- Object Lesson Reckoning: Part 3 -- Caprock Reckoning: Part 4 -- The Way Out When you live in the shadow of a slow-moving crisis, it's natural to tell people about it. At volume. Doubly so when engineers can cheaply and easily address the root causes with minor tweaks. As things worsen, it's also hard not to build empathy for Cassandra. In late 2011, I moved to London, where the Chrome team was beginning to build Google's first "real" browser for Android.1 The system default Android Browser had, up until that point, been based on the system WebView, locking its rate of progress to the glacial pace of device replacement.2 In a world where the Nexus 4's 2GB of RAM and 32-bit, 4-core CPU were the high-end, the memory savings the Android Browser achieved by reusing WebView code mattered immensely.3 Those limits presented enormous challenges for Chromium's safer (but memory-hungry) multi-process sandboxing. Android wasn't just spicy Linux; it was an entirely new ballgame. Even then, it was clear the iPhone wasn't a fluke. Mobile was clearly on track to be the dominant form-factor, and we needed to adapt. Fast.4 Browsers made that turn, and by 2014, we had made enough progress to consider how the web could participate in mobile's app-based model. This work culminated in 2015's introduction of PWAs and Push Notifications. Disturbing patterns emerged as we worked with folks building on this new platform. A surprisingly high fraction of them brought slow, desktop-oriented JavaScript frameworks with them to the mobile web. These modern, mobile-first projects neither needed nor could afford the extra bloat frameworks included to paper over the problems of legacy desktop browsers. Web developers needed to adapt the way browser developers had, but consistently failed to hit the

[Next page](<https://devfeed.tech/topics/chromium.md?cursor=WyIyMDI0LTA4LTEyVDAwOjAwOjAwKzAwOjAwIiwgImNhZDllMWJhLTcwMzAtNGZhZS1iOTVmLWU2N2IyMTdmNjUzOSJd>)