# browsers A browser is a program that retrieves and displays web pages, using a rendering engine to display them. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How WebRTC Scales: Signaling, NAT Traversal, and the Mesh/SFU/MCU Tradeoff DevFeed: [How WebRTC Scales: Signaling, NAT Traversal, and the Mesh/SFU/MCU Tradeoff]() Original publisher: [Read original article]() Author: Karan Pratap Singh Published: 2026-09-15T15:57:39Z Content type: article Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [WebRTC](), [real-time](), [browsers](), [API](), [JavaScript](), [WebSocket](), [Firewall](), [Network](), [servers]() Tags: [api](), [browsers](), [decoding](), [distributed-system](), [firewall](), [http](), [javascript](), [network](), [networking](), [real-time](), [server](), [webrtc]() ### AI overview This article explains how WebRTC enables browsers to exchange audio, video, and data directly. It covers the three WebRTC APIs, signaling through WebSockets or HTTP, NAT traversal using ICE, STUN, and TURN, and the mesh, SFU, and MCU approaches to scaling media delivery. ### Source excerpt Web Real-Time Communication (or WebRTC) is the open standard browsers use to send audio, video, and data straight to each other. There's no plugin or native app, nothing beyond an API that every brows ## How Solaris' Turnstile Influenced the Modern System Designs of Web Browsers and Language Runtimes DevFeed: [How Solaris' Turnstile Influenced the Modern System Designs of Web Browsers and Language Runtimes]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-15T06:06:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [systems](), [Programming](), [Kernel](), [observability](), [browsers](), [web browsers]() Tags: [architecture](), [architecture-design](), [architectures](), [blocking](), [concurrency](), [development](), [efficiency](), [kernel](), [locking](), [memory](), [news](), [observability](), [operating-systems](), [solaris](), [storage](), [systems](), [turnstile-system-design]() ### AI overview The article examines how Solaris innovations influenced modern systems engineering. It discusses the Slab Allocator, OpenZFS, DTrace, Zones, and turnstiles, focusing on how turnstiles reduce per-lock memory overhead while supporting priority inheritance for contended locks. ### Source excerpt Sun's Solaris influenced modern systems engineering, with key innovations like the Slab Allocator for efficient memory management, OpenZFS for advanced storage, and DTrace for observability. Its turnstile mechanism addressed issues with mutexes, promoting lean locking designs that are reflected in contemporary programming languages and web browsers, enhancing performance and memory efficiency. By Olimpiu Pop ## ESP32 Bit Pirate: Bridging Modern Microcontrollers and Browser-Based Hardware Debugging DevFeed: [ESP32 Bit Pirate: Bridging Modern Microcontrollers and Browser-Based Hardware Debugging]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-14T06:06:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [ESP32](), [HTML5](), [browsers](), [Hardware](), [C++](), [Tooling]() Tags: [browser](), [browsers](), [c-plus-plus](), [command-line](), [debugging](), [development](), [development-tools](), [embedded-devices](), [embedded-software-dev](), [esp32](), [esp32-bitpirate-web](), [html5](), [microcontrollers](), [news]() ### AI overview ESP32 Bit Pirate is a browser-based, multi-protocol debugging platform for ESP32-S3 boards. It uses HTML5 APIs such as Web Serial and WebUSB for firmware flashing, terminal access, documentation, and hardware analysis without requiring local development tools. ### Source excerpt ESP32 Bit Pirate project integrates multi-protocol debugging within a browser environment using HTML5 APIs. It enables users to install firmware and interact with microcontrollers like the ESP32-S3 directly from the browser. The platform supports various digital and wireless protocols while providing hands-on guidance through practical recipes for tasks such as memory dumping and signal analysis. By Olimpiu Pop ## Forever a Student DevFeed: [Forever a Student]() Original publisher: [Read original article]() Published: 2026-08-26T00:00:00Z Content type: opinion Language: en Sources: [Jonathan Snook]() Topics: [Web Development](), [Learning](), [CSS](), [browsers](), [Testing](), [Database]() Tags: [blog](), [browsers](), [css](), [development](), [learning](), [testing](), [web-development]() ### AI overview The author reflects on learning web development, sharing work in progress, and accepting that mistakes are part of learning. They describe how writing, prototyping, browser testing, and research help deepen understanding, and argue that people should not be discouraged from sharing what they are learning. ### Source excerpt When I was learning CSS's grid feature (oh gosh, nearly ten years ago), I posted a few short videos talking about my understanding of the feature and how it worked. I was surprised to get scolded for sharing inaccurate information, "especially as a teacher". Wait, what?! Who, me?! I get things wrong all the time. That's part of learning. But it was the teacher remark that threw me because I've never considered myself a teacher. Yes, I've spoken at conferences and put on workshops but the label of teacher isn't one that I feel comfortable with. Perhaps I associate the word with all-knowing authority figures standing in front of a class and I'm far from all-knowing, or an authority, or have much of a figure. I have stood in front of classes, though. I imagine myself more like Stuart from the Mad TV sketch saying "look what I can do!" When I first got into web development, I built a web page that displayed a table pulled from a database. When I showed my friend, he wasn't all that excited. "Is that it?" It was, after all, just a table on a page. (Which, hey, it was 1996. Everything was just a table on a page.) This blog has been a 25+ year journey of me saying "look what I can do" over and over again. I enjoy the process of learning new things and sharing what I've learned. Writing about what I've learned helps me learn even more because I build prototypes and test in different browsers as I try to understand all the nuances of something in my effort to write about a topic. Even with the research and prototypes and testing and writing, I'll get things wrong but one of the things I have learned is not to admonish people sharing what they're learning, even if they get it wrong. We should all be forever a student. Have something to say? Tell me about it. ## The Infinite Scroll Was a Design Crime. Now Meta is Paying for It. DevFeed: [The Infinite Scroll Was a Design Crime. Now Meta is Paying for It.]() Original publisher: [Read original article]() Author: Simon Sterne Published: 2026-08-25T11:30:00Z Content type: opinion Language: en Sources: [Web Designer Depot]() Topics: [web design](), [User experience (UX)](), [Usability](), [Front end](), [Web Development](), [Web](), [Document Object Model (DOM)](), [Software Engineering](), [browser](), [browsers](), [CSS]() Tags: [addictive-design](), [behavioral-design](), [browser](), [browsers](), [css](), [dark-patterns](), [design](), [design-ethics](), [digital-detox](), [digital-wellness](), [dopamine-loops](), [ethical-design](), [front-end-development](), [infinite-scroll](), [meta](), [meta-lawsuit](), [meta-trial](), [social-media-lawsuit](), [software](), [tech](), [tech-ethics](), [tech-industry](), [tech-news](), [ui-ux](), [usability](), [user-experience](), [ux](), [ux-design](), [ux-usability](), [web-design](), [web-development]() ### AI overview The article argues that infinite scroll prioritized addictive engagement and advertising over usability, accessibility of stopping cues, and front-end integrity. It discusses legal scrutiny of Meta's Instagram and Facebook feeds, performance and state-management problems, and calls on web professionals to abandon the pattern. ### Source excerpt The infinite scroll was never a UX feature--it was a slot machine disguised as code. Now, as Meta faces a historic trial over algorithmic addiction, web designers must finally confront the ugly truth: we sacrificed basic usability and human willpower just to keep users trapped in a bottomless pit. ## How Playwright Frameworks get configured with playwright.config.ts DevFeed: [How Playwright Frameworks get configured with playwright.config.ts]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-15T02:30:20Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [Playwright](), [Testing](), [CI/CD](), [browsers](), [Framework]() Tags: [browsers](), [bun](), [bun-create-playwright](), [ci-cd](), [config](), [playwright](), [testing]() ### AI overview This tutorial examines the playwright.config.ts file generated by `bun create playwright`. It explains default test settings, browser projects for Chromium, Firefox, and WebKit, mobile and branded browser configurations, and how retries differ between local runs and CI/CD pipelines. ### Source excerpt When we installed bun, a new package manager owned by Anthropic, then ran "bun create playwright", a new automation framework was stood up, along with sample tests, and a Playwright configuration file. In this post, we will be examining the file generated: playwright.config.ts. Personally, I find the pre-generated file very hard to scan... there are so many options and documentation in the comments, it is difficult for me to focus on the code. Let's examine just the code generated below. If you need to see the whole file, you can see it here: https://playwright.dev/docs/test-configuration Playwright.dev / Configuration mentions, "Playwright has many options to configure how your tests are run. You can specify these options in the configuration file". What is Configured By Default? import { defineConfig, devices } from '@playwright/test'; export default defineConfig({ testDir: './tests', fullyParallel: true, forbidOnly: !!process.env.CI, retries: process.env.CI ? 2 : 0, workers: process.env.CI ? 1 : undefined, reporter: 'html', // baseURL: 'http://localhost:3000', /* Collect trace when retrying the failed test. See https://playwright.dev/docs/trace-viewer */ trace: 'on-first-retry', }, /* Configure projects for major browsers */ projects: [ { name: 'chromium', use: { ...devices['Desktop Chrome'] }, }, { name: 'firefox', use: { ...devices['Desktop Firefox'] }, }, { name: 'webkit', use: { ...devices['Desktop Safari'] }, }, }); I know what you are thinking ... What the heck is process.env.CI ? 2 : 0? This is know as a ternary operator. It is a shorthand for: "If A then B, else C". You can run tests two ways: Locally, on your local machine, or through a CI / CD Pipeline like Jenkins, GitHub Actions, or GitLab. If you are running tests on CI / CD, the process.env.CI would automatically get set. Since A is true, the value of retries would be "2". If you are running tests locally, the process.env.CI would NOT get set. Since A is false, the value "0" would be selected. CI / ## Announcing a Trillion Dollar Security grant for WEBCAT DevFeed: [Announcing a Trillion Dollar Security grant for WEBCAT]() Original publisher: [Read original article]() Author: Ethereum Foundation Access Cluster Published: 2026-08-05T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Security](), [Open Source](), [browsers](), [Front end](), [Firefox]() Tags: [announce](), [browsers](), [ethereum](), [firefox](), [front-end](), [funding-coordination](), [open-source](), [security](), [signing](), [supply-chain-attacks](), [web-applications]() ### AI overview The Ethereum Foundation's Trillion Dollar Security initiative announced a grant to the Freedom of the Press Foundation to support continued development of WEBCAT, an open source tool that enables browsers to verify whether code served by enrolled websites matches code published by their developers. The grant will also support bringing this protection to Ethereum wallets and apps. ### Source excerpt The Ethereum Foundation's Trillion Dollar Security (1TS) initiative is proud to announce a grant allocation to Freedom of the Press Foundation (FPF) to support the continued development of WEBCAT. WEBCAT is an open source tool that lets browsers verify that code served by an enrolled website matches what its developers... ## The Electron browser is being deprecated in Cypress DevFeed: [The Electron browser is being deprecated in Cypress]() Original publisher: [Read original article]() Published: 2026-07-10T15:15:58Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Electron](), [Testing](), [browsers](), [Chromium](), [Continuous integration]() Tags: [browser](), [browsers](), [chrome](), [chromium](), [continuous-integration](), [cypress](), [edge](), [firefox](), [testing]() ### 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. ## PACT: Anonymous Credentials for the Web DevFeed: [PACT: Anonymous Credentials for the Web]() Original publisher: [Read original article]() Author: Dennis Jackson Published: 2026-06-23T15:29:52Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Web](), [browsers](), [AI Bots](), [Tooling]() Tags: [agent](), [blog](), [bots](), [browsers](), [developer](), [firefox](), [mozilla](), [privacy](), [security](), [technical](), [web]() ### AI overview This technical companion examines PACT, a proposed approach to anonymous credentials for the web. It describes how anti-abuse systems, privacy protections, generative AI, VPN use, and browser-based AI agents create tension between preventing abuse and preserving privacy and user choice. ### Source excerpt This is the technical companion to our update on Distilled, "Keeping the web open and private in the bot era." Here we take a deeper look at the problem space, the design we're proposing, and the problems still left to solve. Bots (and privacy-preserving browsers) not welcome Browse a news site in a private window. Shop [...] The post PACT: Anonymous Credentials for the Web appeared first on Mozilla Hacks - the Web developer blog. ## Bringing Goodnotes to the web with Swift and WebAssembly DevFeed: [Bringing Goodnotes to the web with Swift and WebAssembly]() Original publisher: [Read original article]() Author: Yuta Saito Published: 2026-06-01T12:00:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [WebAssembly](), [cross-platform](), [web applications](), [iOS](), [browsers]() Tags: [browsers](), [code](), [cross-platform](), [ios](), [performance](), [swift](), [web-applications](), [webassembly]() ### AI overview Goodnotes describes bringing its existing Swift-based iOS note-taking experience to web browsers by compiling Swift to WebAssembly. The approach reuses a large, performance-critical codebase and preserves consistent ink rendering and behavior across platforms. ### Source excerpt Goodnotes has been helping millions of users take handwritten notes on iPad for over a decade, earning recognition as Apple's iPad App of the Year in 2022. Today, the same Swift code that powers our iOS app also runs seamlessly in web browsers through WebAssembly, delivering the exact same ink rendering and note-taking experience users love. This journey demonstrates that Swift excels as a cross-platform language, running high-performance applications while sharing the same codebase. Every bug fix and improvement to Goodnotes benefits all our users simultaneously, regardless of which platform they use. After two years of development and over two years in production at Goodnotes, we've shown that Swift on WebAssembly is a viable, powerful approach for building complex, performance-critical web applications. Why we chose Swift for the web When we decided to bring Goodnotes to the web in 2021, we faced a critical decision. After more than 10 years of development, we had accumulated millions of lines of Swift code that implemented countless refinements and optimizations for digital ink rendering, document synchronization, conflict resolution using Conflict-Free Replicated Data Types (CRDTs), and content search and document indexing. We need to maintain more than 60 Frames Per Second (FPS) for real-time ink rendering, which makes performance critical. A JavaScript rewrite, Flutter, or Kotlin Multiplatform would all require rewriting our entire rendering engine from scratch, a substantial undertaking that would have delayed our web launch by years and inevitably introduced behavioral differences between platforms. SwiftWasm emerged as the solution. This community-driven project allows Swift code to compile to WebAssembly, running in browsers with good performance. We started experimenting with SwiftWasm, building prototypes to validate the approach. Our first experiment focused on our handwriting component, a performance-critical part of Goodnotes that would serve as a go ## New to the web platform in May DevFeed: [New to the web platform in May]() Original publisher: [Read original article]() Author: Rachel Andrew GitHub LinkedIn Mastodon Bluesky Homepage Published: 2026-05-29T07:00:00Z Content type: article Language: en Sources: [web.dev: Blog]() Topics: [Web platform](), [Web](), [browsers](), [web browsers](), [CSS](), [HTML](), [picture-in-picture](), [API](), [Chrome](), [Firefox]() Tags: [api](), [audio](), [browsers](), [chrome](), [css](), [firefox](), [html](), [performance](), [picture-in-picture](), [web](), [web-browsers](), [web-platform]() ### AI overview A roundup of notable web platform features that became available in stable or beta browsers during May 2026, including CSS pseudo-classes, name-only container queries, container style queries for custom properties, native lazy loading for video and audio, and the Document Picture-in-Picture API. ### Source excerpt Discover some of the interesting features that have landed in stable and beta web browsers during May 2026. ## Why Developers Should Avoid Reimplementing Browser Features in Website Design DevFeed: [Why Developers Should Avoid Reimplementing Browser Features in Website Design]() Original publisher: [Read original article]() Published: 2026-05-23T00:00:00Z Content type: opinion Language: en Sources: [Susam Pal]() Topics: [web design](), [Website](), [browsers](), [User Experience](), [Development]() Tags: [browsers](), [developers](), [modern-web-design](), [web-design](), [website]() ### AI overview This opinion article argues that web developers should avoid reimplementing browser-provided behaviors such as scrolling, link navigation, text selection, context menus, copy and paste, password fields, and date pickers when users depend on the native behavior. It compares this practice with the cryptographic principle of avoiding private, unreviewed implementations. ### Source excerpt This is going to be a rant about modern web design practices. But before I get to that, let me begin with a familiar principle from the world of cryptography. Among software developers, and especially among those who work on security-sensitive systems, there is a well-known maxim: Don't roll your own crypto. This does not mean that nobody is allowed to write cryptographic code. Someone has to. It means that, for ordinary production software that protects sensitive data of users, we should not rely on a private, unreviewed implementation that has not been vetted by the wider software development community. We should use established, vetted software packages or tools wherever possible. Fortunately, it is now standard industry practice to avoid rolling your own crypto and instead use cryptographic algorithms and packages that have been peer reviewed and stood the test of time. It wasn't so some twenty years ago. I have seen several flawed home-grown RC4 implementations early in my career, with issues like improper initialisation vectors, predictable keystreams and partial leakage of plaintext into ciphertext, putting sensitive data of users at risk. But today, major e-commerce websites or banks typically do not use home-grown cryptography for its web services. In fact, in regulated domains such as payments, healthcare and personal data processing, doing so could violate requirements for strong cryptography, possibly leading to hefty financial penalties. Website design is obviously not cryptography. A broken scroll bar is not the same kind of failure as a broken encryption scheme. But I wish there were a similar maxim for website design as well. There are many aspects of websites where, I think, developers should not be rolling their own X, especially when X is something browsers already do well and something users depend on every day. Here I present a list of such X. Don't roll your own page scrolling. Don't roll your own link navigation. Don't roll your own text selec ## Trustworthy JavaScript for the Open Web DevFeed: [Trustworthy JavaScript for the Open Web]() Original publisher: [Read original article]() Author: Firefox Security Team Published: 2026-05-05T15:49:11Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [JavaScript](), [Web platform](), [web applications](), [browsers](), [End-to-End Encryption](), [Encryption](), [Security](), [Firefox Nightly](), [Cloudflare]() Tags: [applications](), [browsers](), [cloudflare](), [encryption](), [firefox](), [firefox-nightly](), [javascript](), [meta](), [open](), [security](), [web](), [web-platform]() ### AI overview Mozilla presents WAICT, a web platform proposal for making client-side JavaScript more trustworthy when servers may be malicious or compromised. It binds delivered code to a developer-supplied manifest, records manifests in a publicly auditable log, and enables browsers to reject code that has not been logged. An early prototype is available behind a preference in Firefox Nightly. ### Source excerpt The open web is a critical platform for applications that handle highly sensitive data, from private communications to financial transactions and medical records. Traditionally, servers are trusted to deliver the appropriate code and resources for their web applications to browsers, who then provide a secure and isolated environment for their execution. In some circumstances, this [...] The post Trustworthy JavaScript for the Open Web appeared first on Mozilla Hacks - the Web developer blog. ## How OpenAI delivers low-latency voice AI at scale DevFeed: [How OpenAI delivers low-latency voice AI at scale]() Original publisher: [Read original article]() Published: 2026-05-04T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [voice ai](), [WebRTC](), [Artificial Intelligence](), [OpenAI](), [Latency](), [Low Latency](), [real-time](), [API](), [browsers](), [client](), [ChatGPT](), [Server]() Tags: [ai](), [api](), [audio](), [browsers](), [chatgpt](), [engineering](), [global](), [latency](), [low-latency](), [network](), [openai](), [real-time](), [server](), [servers](), [speech](), [speed](), [voice-ai](), [webrtc]() ### AI overview OpenAI describes a rearchitected WebRTC stack for delivering low-latency voice AI at global scale. The article explains how split relay and transceiver components address connection setup, stateful media sessions, routing, and stable media round-trip performance while preserving standard WebRTC behavior for clients. ### Source excerpt How OpenAI rebuilt its WebRTC stack to power real-time Voice AI with low latency, global scale, and seamless conversational turn-taking. ## Protecting Cookies with Device Bound Session Credentials DevFeed: [Protecting Cookies with Device Bound Session Credentials]() Original publisher: [Read original article]() Author: Google (noreply@blogger.com) Published: 2026-04-09T17:07:00Z Content type: release Language: en Sources: [Google Online Security]() Topics: [Security](), [Chrome](), [browsers](), [Malware](), [Windows](), [macOS](), [trusted-execution-environment]() Tags: [browser](), [chrome](), [files](), [macos](), [malware](), [memory](), [none](), [security](), [tokens](), [windows]() ### AI overview Google announces that Device Bound Session Credentials (DBSC) is entering public availability for Windows users on Chrome 146, with macOS support planned for an upcoming Chrome release. DBSC binds authentication sessions to a device-backed key so exfiltrated session cookies cannot be used to access accounts. ### Source excerpt Posted by Ben Ackerman, Chrome team, Daniel Rubery, Chrome team and Guillaume Ehinger, Google Account Security team Following our April 2024 announcement, Device Bound Session Credentials (DBSC) is now entering public availability for Windows users on Chrome 146, and expanding to macOS in an upcoming Chrome release. This project represents a significant step forward in our ongoing efforts to combat session theft, which remains a prevalent threat in the modern security landscape. Session theft typically occurs when a user inadvertently downloads malware onto their device. Once active, the malware can silently extract existing session cookies from the browser or wait for the user to log in to new accounts, before exfiltrating these tokens to an attacker-controlled server. Infostealer malware families, such as LummaC2, have become increasingly sophisticated at harvesting these credentials. Because cookies often have extended lifetimes, attackers can use them to gain unauthorized access to a user's accounts without ever needing their passwords; this access is then often bundled, traded, or sold among threat actors. Crucially, once sophisticated malware has gained access to a machine, it can read the local files and memory where browsers store authentication cookies. As a result, there is no reliable way to prevent cookie exfiltration using software alone on any operating system. Historically, mitigating session theft relied on detecting the stolen credentials after the fact using a complex set of abuse heuristics - a reactive approach that persistent attackers could often circumvent. DBSC fundamentally changes the web's capability to defend against this threat by shifting the paradigm from reactive detection to proactive prevention, ensuring that successfully exfiltrated cookies cannot be used to access users' accounts. How DBSC Works DBSC protects against session theft by cryptographically binding authentication sessions to a specific device. It does this using hardwar ## How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today DevFeed: [How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today]() Original publisher: [Read original article]() Author: Scott Jehl Published: 2026-04-07T14:30:00Z Content type: tutorial Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [HTML](), [lazy loading](), [web-standards](), [browsers](), [Web Development]() Tags: [audio](), [best-practices](), [browsers](), [gotchas](), [how-to](), [html](), [lazy-loading](), [video]() ### AI overview This tutorial explains how to use standard HTML video and audio lazy loading on websites. It covers recommended practices and common implementation pitfalls, noting that the feature is gaining support in major browsers. ### Source excerpt HTML video and audio lazy loading is now a web standard and quickly gaining support in all major browsers. Given Squarespace's role in proposing and implementing it, we're very excited to see how developers use it on the web. Let's cover some best practices for using video and audio lazy loading in any website, as well as some gotchas to avoid. ## The Web Is An Antitrust Wedge DevFeed: [The Web Is An Antitrust Wedge]() Original publisher: [Read original article]() Author: Alex Russell Published: 2026-04-03T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [Web](), [interoperability](), [browsers](), [Mobile](), [App]() Tags: [apple](), [apps](), [browsers](), [competition](), [interoperability](), [regulatory](), [web](), [web-apps](), [webdev]() ### AI overview This opinion argues that browsers and progressive web apps should be central to antitrust efforts targeting mobile ecosystems. It contends that regulators are accepting weak enforcement and that focusing mainly on alternative native app stores may leave the existing mobile duopoly's power intact. ### Source excerpt TL;DR: Armed with new powers to rein in the worst excesses of mobile's duopolists, antitrust bodies around the world are struggling to find their footing, and an incurious tech press is letting it pass with nary a nod. Browsers are app stores, but that perspective is almost entirely absent from the antitrust conversation. Instead of prioritising the one, narrow intervention that can safely unlock maximal competition, regulators are gripped by alt store fever dreams; driving down cul-de-sacs that will leave the duopolists' power intact even if new native app stores materialise. Worse, enforcers of new regulations are choking in the face of blatant non-compliance. Laws designed to kickstart competition and unchain web apps are being flouted, but regulators seem unfazed. The web is an engine of interoperability; this was understood by the drafters of these laws, but enforcers have not internalised the lesson, with the UK's CMA being only the latest to pose capitulation as success. Instead of unlocking growth and dynamism, overcautious regulators are ratifying non-compliance through inaction. Timidity today reduces room for manoeuvre tomorrow while hampering home-grown competitors to Big Tech. As it did twenty-five years ago, the web can unlock maximum change with the lowest risk, but regulators are falling down on the job, and tech reporters are not informing readers of the options or the stakes. It's time we spoke plainly about these overlapping institutional failures. Contents Open Societies Necessitate Interoperability Shared Premises Alt Stores, PWAs, and the App Store Endgame Regulators Are Missing The Ripest Opportunity Cupertino is Running Circles Around Brussels, Tokyo, and London Browsers Are App Stores Our Tech Press is Missing the Story, Too It's a day that ends in "y", which means The Verge is at it again: covering the regulatory tussle over mobile ecosystems without mentioning browsers, the web, or PWAs. This long-established pattern is as frustrating as i ## The state of agent traffic in documentation (March 2026) DevFeed: [The state of agent traffic in documentation (March 2026)]() Original publisher: [Read original article]() Author: Han Wang Published: 2026-04-03T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [ai-coding](), [Claude Code](), [cursor](), [Cloudflare](), [browsers]() Tags: [2026](), [agent](), [agents](), [ai](), [ai-agents](), [ai-coding](), [ai-coding-agents](), [ai-trends](), [analysis](), [browsers](), [caveat](), [claude-code](), [cloudflare](), [cursor](), [documentation](), [edge](), [firefox](), [http]() ### AI overview Mintlify analyzes 30 days of Cloudflare traffic across its documentation sites and finds that AI coding agents accounted for 45.3% of requests, nearly matching traditional browser traffic at 45.8%. Claude Code and Cursor generated 95.6% of identified AI-agent traffic, while OpenAI Codex could not be distinguished because it does not provide an identifying user-agent header. ### Source excerpt An analysis of 30 days of Mintlify documentation traffic, broken down by AI agents, browsers, and other sources. ## Navigating Regional Network Blocks DevFeed: [Navigating Regional Network Blocks]() Original publisher: [Read original article]() Author: Sara Read Published: 2026-03-26T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Network](), [hosting](), [browsers](), [Pull Request](), [Security](), [Mozilla]() Tags: [applications](), [browsers](), [hosting](), [internet](), [mozilla](), [network](), [platforms](), [pull-request](), [security]() ### AI overview Supabase explains how regional ISP and government-directed domain blocks affect multi-tenant infrastructure platforms. Drawing on three incidents, the article discusses causes, responses, and preventive measures, including adding hosting domains to the Public Suffix List to establish tenant boundaries in browsers. ### Source excerpt A look at recent ISP and government-directed blocks of Supabase domains in three regions--what triggered them, how we worked with authorities and customers to restore access, and what multi-tenant platforms can do to prepare. ## You can use newline characters in URLs DevFeed: [You can use newline characters in URLs]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-02-28T19:21:39Z Content type: tutorial Language: en Sources: [Daniel Lemire]() Topics: [Web](), [browsers](), [HTML](), [SVG](), [Parsing](), [data]() Tags: [ascii](), [browsers](), [code](), [graphics](), [html](), [parsing](), [svg](), [web](), [xml]() ### AI overview This article explains that HTML URLs can contain newline and tab characters in practice because the URL parser reports a validation error but removes those characters and continues. It also describes how ASCII whitespace is handled in data URLs, including base64-encoded PNG and SVG images. ### Source excerpt We locate web content using special addresses called URLs. We are all familiar with addresses like https://google.com. Sometimes, URLs can get long and they can become difficult to read. Thus, we might be tempted to format them like so in HTML using newline and tab characters, like so: my blog post It will ... Continue reading You can use newline characters in URLs ## Launching Interop 2026 DevFeed: [Launching Interop 2026]() Original publisher: [Read original article]() Author: Jake Archibald Published: 2026-02-12T17:07:24Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Web](), [Web platform](), [web-standards](), [browsers](), [Test coverage](), [dashboards](), [WebRTC](), [view transitions](), [CSS]() Tags: [apple](), [browser](), [css](), [featured-article](), [firefox](), [google](), [interop](), [microsoft](), [mozilla](), [uncategorized](), [view-transitions](), [web](), [web-developers](), [web-platform](), [webrtc]() ### AI overview Mozilla's Interop Project is launching Interop 2026, continuing its cross-browser effort to improve web compatibility through shared priorities and Web Platform Tests. The article reviews Interop 2025's progress, including higher overall scores, broader cross-browser support for major web platform features, and improved reliability for existing features such as WebRTC, CSS Flexbox, and CSS Grid. ### Source excerpt The Interop Project is a cross-browser initiative to improve web compatibility in areas that offer the most benefit to both users and developers. The group, including Apple, Google, Igalia, Microsoft, and Mozilla, takes proposals of features that are well defined in a sufficiently stable web standard, and have good test suite coverage. Then, we come [...] The post Launching Interop 2026 appeared first on Mozilla Hacks - the Web developer blog. ## Interop 2026: Continuing to improve the web for developers DevFeed: [Interop 2026: Continuing to improve the web for developers]() Original publisher: [Read original article]() Author: Rachel Andrew GitHub LinkedIn Mastodon Bluesky Homepage Published: 2026-02-12T08:00:00Z Content type: article Language: en Sources: [web.dev: Blog]() Topics: [Web platform](), [interoperability](), [web-standards](), [CSS](), [dialog](), [view transitions](), [browsers](), [dashboards]() Tags: [browsers](), [css](), [developers](), [dialog](), [interop](), [interoperability](), [view-transitions](), [web](), [web-platform]() ### AI overview Interop 2026 is an effort by browser-engine contributors to improve web-platform interoperability. It focuses on high-priority issues for web developers and users, including anchor positioning, container style queries, dialogs and popovers, scroll-driven animations, and view transitions. ### Source excerpt Learn about the features included in Interop 2026. ## Credential stuffing: What it is and how to protect yourself DevFeed: [Credential stuffing: What it is and how to protect yourself]() Original publisher: [Read original article]() Author: Christian Ali Bravo Published: 2026-01-08T10:00:00Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [passwords](), [Cybercrime](), [Malware](), [Bot](), [browsers](), [Forms]() Tags: [apis](), [attacks](), [bots](), [breach](), [browsers](), [cybercrime](), [digital-security](), [forms](), [malware](), [passwords]() ### AI overview The article explains credential stuffing, in which attackers automate the use of previously exposed username-and-password pairs against online services. It describes how password reuse, data breaches, infostealer malware, bots, and automated tools enable attacks, and contrasts credential stuffing with brute-force attacks. ### Source excerpt Reusing passwords may feel like a harmless shortcut - until a single breach opens the door to multiple accounts ## Browser support for RFC9460 HTTPS DNS records DevFeed: [Browser support for RFC9460 HTTPS DNS records]() Original publisher: [Read original article]() Published: 2025-12-12T22:00:01Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [browsers]() Tags: [2025](), [browsers](), [dns](), [https]() ### AI overview A quick summary of browser support for RFC9460 HTTPS DNS records and the extent of that support as of December 2025. ### Source excerpt A quick summary of which browsers support RFC9460 HTTPS DNS records and to what extent as of December 2025. [Next page]()