Non-profit internet organization behind Firefox and related open-source projects, long focused on user privacy.
Chrome has released Modern Web Guidance 1.0, a stable skill set that injects expert-reviewed web platform best practices and cross-browser compatibility data directly into coding agents. Version 1.0 adds a modernization workflow that scans existing codebases, an expanded guidance database, a public evaluation dashboard, and expands into a cross-browser initiative with Firefox and Edge.
Mozilla has shipped a new round of fingerprinting protections in Firefox that reduce extractable distinguishing details, making more users look alike to tracking scripts and blunting cross-site identification. The work builds on Mozilla's large-scale measurement research on browser and device fingerprinting, accepted at CCS 2026, with findings and code shared openly.
Mozilla, with the University of Toronto and UC San Diego, ran a large-scale browser fingerprinting study across nearly 25 million Firefox release users to quantify real-world identifiability and isolate which characteristics make users unique. The findings directly shaped the fingerprinting protections shipped in Firefox 143, and the team released the paper, full appendix data, privacy-preserving aggregate datasets, analysis code, and an interactive self-test tool.
Google Chrome, Microsoft Edge, Mozilla Firefox and MDN have jointly released Modern Web Guidance, a skill set that embeds web platform best practices and browser compatibility data directly into coding agents to steer them away from legacy JavaScript patterns. It ships with an npx install wizard and a legacy-scan detector trained on 30k GitHub repos to flag outdated patterns for modernization.
Datasette author Simon Willison found that Firefox automatically prefetches the next page of rows based on the link rel=next HTTP header, causing wasted rendering and bandwidth for the vast majority of visitors who never click through. He changed Datasette to stop sending that header to Firefox for HTML pages. The underlying Mozilla bug has been open for 24 years, and his own 2002 blog post on the behavior had been entirely forgotten.