Firefox 154 Adds Better Building Blocks for Multi-Region Browser Testing

Firefox 154 was released on August 18, 2026. Its WebDriver BiDi updates are not proxy-product features, but several of them can make authorized multi-region browser testing easier to isolate, diagnose, and reproduce.

The most relevant changes for teams running localization QA, ad verification, market research, or other approved browser workflows are a new user-context identifier in multiple events and commands, worker-aware language-header overrides, and browsing-context screencast commands.

User-context identifiers improve isolation

WebDriver BiDi now includes a userContext field in the payload of several events and commands. In Firefox, a user context is associated with a container-like browser environment.

This matters when one automation process runs several regional or customer-specific sessions. Without a reliable context identifier, network, console, script, and navigation events can be difficult to attribute when they arrive concurrently. Explicit attribution makes it easier to connect each event with the intended proxy route, locale, cookie jar, and test case.

The feature does not automatically isolate every application resource. Teams should still use separate credentials, storage boundaries, proxy session identifiers, and clear lifecycle controls.

Locale override now reaches worker requests

Firefox 154 updates emulation.setLocaleOverride so the Accept-Language header can also be overridden for fetch and WebSocket requests made by workers.

This closes an important consistency gap for localization tests. A page can display one locale while a dedicated or shared worker requests data with a different language preference. That mismatch may produce mixed-language content or region-specific API responses that are difficult to reproduce.

For proxy-based testing, location and language should be treated as separate variables. An exit in one country does not guarantee the browser sends the desired language header. Test both explicitly.

Screencast commands add visual evidence

The release implements browsingContext.startScreencast and browsingContext.stopScreencast, which record a browsing context and save the result as video.

Visual evidence can help diagnose geo-specific layouts, consent dialogs, redirects, loading states, and timing-sensitive failures. A recording should complement structured logs rather than replace them. Protect personal data and credentials, define retention rules, and record only authorized workflows.

A practical migration checklist

1. Pin the browser version

Run a controlled comparison between the currently approved Firefox build and Firefox 154. Record the WebDriver client version as well because protocol support depends on both sides.

2. Map every test to a user context

Assign one context per independent workflow where practical. Include the context identifier in event logs, proxy-session metadata, and result records. Verify that closing a test also releases its context and network resources.

3. Test location and language as a matrix

For each approved region, test at least the intended language plus one control language. Confirm the page, fetch requests, and worker WebSocket traffic use the expected language preference.

4. Capture evidence selectively

Enable screencast only for failing samples, canaries, or a small diagnostic percentage. Continuous recording can increase storage, processing, and privacy exposure.

5. Correlate browser and proxy telemetry

Link the user context, proxy session, requested region, exit observation, navigation identifier, status, and validation outcome. Never put proxy credentials, cookies, or tokens in routine logs.

6. Recheck waits and navigation behavior

Firefox 154 also fixes a case where navigation could resolve prematurely for subframes after history.replaceState or navigation to an error page. Retest workflows that depend on subframe completion and error-page handling instead of assuming existing waits remain correct.

What this release does not guarantee

• It does not guarantee geographic accuracy of a proxy route.
• It does not make every site safe or authorized to automate.
• It does not replace content validation with visual recording.
• It does not ensure all WebDriver clients expose every new command immediately.
• It does not remove the need for rate limits, privacy controls, and test isolation.

Release-readiness checklist

• Confirm Firefox 154 and the chosen WebDriver client are compatible.
• Attribute events and commands to the correct user context.
• Validate proxy route and language preference independently.
• Include worker fetch and WebSocket behavior in locale tests.
• Record only the minimum visual evidence needed.
• Sanitize logs and recordings before retention.
• Test subframe navigation and error pages.
• Keep the previous browser version available for rollback.

FAQ

Does Firefox 154 configure the proxy automatically per user context?

No. The release-note changes discussed here improve context attribution and testing capabilities. Proxy configuration still needs to be provided through the supported automation and browser configuration mechanisms.

Can a screencast prove the correct exit location?

No. It can show visible page behavior, but exit location should be verified through network telemetry and approved location checks.

Should every automated run be recorded?

Usually not. Selective recording reduces storage and privacy risk while preserving evidence for canaries and failures.

Source note: Mozilla MDN, Firefox 154 release notes for developers, released August 18, 2026 and reviewed August 19, 2026.

Use browser automation and proxy infrastructure only for lawful, authorized work. Respect site terms, privacy requirements, rate limits, and data-protection obligations. Related operations guidance is available at 98IP.