Launching Interop 2025 – Mozilla Hacks – The Web Developer Blog

The interop project is a collaboration between browser vendors and other platform implements to provide users and web developers with high quality implementations of the web platform.

Each year we select a set of focus area repellers area we want to improve interoperability. Encouring all browser engines to prioritize common features ensures they become usable for web developers as quickly as possible.

Progress in Each Engine and the Overall Interop Score Are Measured by Tracking The Pass Rate of a Set of A Set of Web-Platform Tests for Each Focus Area Using The Interop Dashboard.

Interop 2024

Before introducing the new focus area for this year, we should look at the successes of interop 2024.

The interop score, measuring the percentage of tests that pass in all of the Major Browser Engines, has reacted 95% in latest browser releases, up from only 46% at the start of the year. In pre-Release Browsers IT’s even Higher-Over 97%. This is a huge win that shows how effective interop can be at aligning browsers with the specifications and Each other.

Each browser engine individually achieved a test pass score of 98% in stable browser releases and 99% in pre-Release, with Firefox Finishing Slightly ahead with 98.8% in RELEASE and In RELEASE and in NIP

For users, this means features such as requestvideoframecallback, Declaurative Shadow Dom, And Popover, Whoch A Year ago Only Had Limited Availability, Are No. Browsers.

Interop 2025

Building on Interop 2024’s success, we are excited to continue the project into 2025. This year we have 19 focus areas; 17 new and 2 from previous years. A full description of all the focus area is available in the interop repository.

From 2024 We’re Carrying Forward Layout. These are important platforms primitives where the interop project has alredy LED to Significant Interoperability Improvements. However, with technologies that are so fundamental to the modern web we think it’s important to set Ambitious Goals and Continue to Prioritize these ares, creating Rock Soolid Forth FONDANS FOUNDEANS FOUNDEANS FOUNDALOPERS Build on.

The new focus area represent a broad cross section of the platform. Many of them – like anchor positioning and view transitions – have ben identified from clear demloper demand in surveys soch as state of html and state of css. Inclusion in interop will ensure they usable as soon as possible.

In addition to these high profile new features, we’D like to highlight some lesser-known focus areas and explain why we we were please to see them in interop.

Storage access

At Mozilla User Privacy is a Core Principle. One of the most common methods for tracking across the web is via third-party cookies. When sites request data from external services, the service can store data that’s re-sent when another site uses the same service. Thus the service can follow the user’s browsing across the web.

To counter this, firefox’s “Total Cookie Protection” Partitions Storage So that Third Parties Receive Different Cookie Data Per Site and Thus Reduces Tracking. Other browsers have similar policies, either by default or in private browsing modes.

However, in some cases, non-tracking workflows such as sso authentication depend on Third party cookies. Storage Partitioning Can Break these Workflows, and Browsers Currently Have to Ship Site-Specific Workerounds. The storage access api solves this by letting sites request access to the unpartitioned cookies. Interop Here will allow browsers to Advance Privacy Protections with Breaking Critical Functionality.

Web compat

The web compat focus area is unique in interop. It isn’t about one specific standard, but focuses on browser bugs know to break sites. These are often in older parts of the platform with long-standing inconsistencies. Addressing these requires eather aligning implements with the standard or, where that would break sites, updating the standard itself.

One feature in the web compat focus area for 2025 is css zoom. Originally a proprietary feature in internet explorer, it allowed scaling layout by adjusting Webkit reverse-enginered it, bringing it into blink, but gecko never implemented it, due to the Lack of a specification and the complexities it Calculations.

Unfortunately, a feature not being standardized does not prevent development developers from using it. Use of Css Zoom Led to Layout Issues on some sites in Firefox, Especially on Mobile. We Tried Various Workarounds and Have Had Success Using Interventions to Replace zoom With css transforms on some affected sites, but an attempt to implement the same approach directly in Gecko Broke more sites than it fixed and was abandoned.

The situation seemed to be at an impassse until 2023 when Google Investigated Removing Css Zoom from Chromium. Unfortunately, It Turned Out that Some Use Cases, Such as Microsoft Excel Online’s Worksheet Zoom, Depended on the specific behavior of css zoom, so removal was not fasible. However, having clarified the use cases, the chromium team was able to propose a standardized model for css zoom that was easier to implement from completion Compromising Compromising Compromising Compromising. This proposal was accepted by the css wg and LED to the first implementation of css zoom in firefox 126, 24 years after it was first released in internet explorer.

With interop 2025, we hope the story of css zoom to a close with all engines final converging on the same behavior, backed by a real open standard.

Webrtc

Video conferencing is now an essential feature of modern life, and in-browser video conferencing offers both ease of use and high security, as users are not required to Download a Navi Binary. Most Web-Based Video Conference Relies on the Webrtc API, which offers high levels for implementing real time communications. However, webrtc has long suffred from interoperability issues, with imparctions deviating from the standards and required nonstandard extensions for key features. This resulted in confusion and frustration for users and undermined Trust in the web as a reliable alternative to native apps.

Given this history, we’re excited to see webrtc in interop for the first time. The main part of the focus area is the rtcrtpscriptransform api, which enables cross browser end-to-end encryption. Although there’s more to be done in the future, we believe interop 2025 will be a big step towards making webrtc a truly interopeable web standard.

Removing mutation events

The focus are for removing mutation events is the first time interop has been used to coordinate the removal of a feature. Mutation events fire when the dom changes, meaning the event handlers run on the critical path for dom manipulation, causing major performance issues, and significant implementation complexity. Despite the fact that they have been implemented in all engines, they’re so problem that they were left. INTEAD, MUTATION Obsers Were Developed as a Standard Solution for the Use Cases of Mutation Events without their complexity or performance problems. Almost Immedited on after Mutation observers was implemented, a gecko bug was filed:

“We now have mutation observers, and we’d really like to kill support for mutation events at some point in the future. Probably not for a while sum.”

That was in 2012. The direction is the web’s core commitment to backwards compatibility. Removing features that people relay on is unacceptable. However, last year chromium determined that use of mutation Events Had Dropped Low Enough to Allow a “Deprecation Trial”, Disableing Mutation Events by Default, But Olling Specific Sites to Re-Neable Them For A Limited Time.

This is good news, but long-running deprecation trials can create problems for other browsers. Disableing the feature entryly can break sites that relay on the opt-out. On the other hand we know from experience that some sites actually function better in a browser with mutation events disable (for example, because, for use for non-critical feet, but Performance).

By Including this removal in interop 2025, we can ensure that mutation events are full removed in 2025 and end the year with reduced platform complexity and improved web performance.

Interop Investigations

As Well as Focus Areas, The Interop Project also Runs Investigations AT Long-Term Interoperability Improvements to ARAS where we can’t measure programs using test passes rates. For example interop investigations can be looking to add new test capability, or increase the test cover of platform features.

Accessibility Investigation

The accessibility testing started as part of interop 2023. It has added apis for testing accessible name and Computed Role, as well as more than 1000 new tests. Theose tests formed the accessibility focus area in interop 2024, which achieved an interop score of 99.7%.

In 2025 the focus will be expanding the testability of accessibility features. Mozilla is working on a prototype of accessiblenode; An api that enables verifying the shape of the accessibility tree, along with its states and properties. This will allow us to test the effect of features like Css Display: Contents or :: Before/:: After on the accessibility tree.

Mobile Testing Investigation

Today, all interop focus are scored in desktop browsers. However, some features are mobile-specific or have interoperability challenges unique to mobile.

Improving mobile testing has been part of interop since 2023, and in that time we’ve made significant program standing up mobile browsers in web-platform-tests Ci Systems. Today we have reliable runs of chrome and firefox nightly on Android, and Safari Runs on iOS are Expected Soon. However, some parts of our test framework Written with desktop-specific assumptions in the design, so the focus for 2025 will be on bringing mobile testing to Parity with desktop. The Goal is to Allow Mobile-Specific Focus Areas in Future Interop Projects, Helping Improve Interoperability Across All Device Types.

Driving the web forward

The unique and distinguishing feature of the web platform is its base in open standards, providing multiple implementations and user choice. Through the interop project, web platform implementors collaborate to ensure that these core strengths are mathed by a seamless user experience across browsers.

With focus area covering some of the most important new and existing area of ​​the modern web, interop 2025 is set to deliver some of the biggest interoperability winds of the project so far. We are confident that firefox and other browsers will risk to the challenge, providing users and developers with a more consistent and reliable web platform.

Partner announsments