Skip to content

[Bug]: locale is not propagated to workers in firefox #38919

Closed

Description

@Skn0tt

Version

95a728a

Steps to reproduce

it('should format number in workers', async ({ browser, server }) => {

This test passes in CI, but not locally. I assume it's because CI locale happens to give the same output as es-MX. If you change the locale to ru-RU, it should also fail in CI.

It seems that workers are not respecting the context locale.

Expected behavior

Workers should be respecting context locale.

Actual behavior

Workers are using system locale.

Additional context

found during microsoft/playwright-python#3026

Environment

System:
    OS: macOS 26.2
    CPU: (12) arm64 Apple M3 Pro
    Memory: 133.67 MB / 18.00 GB
  Binaries:
    Node: 20.19.0 - /Users/skn0tt/.local/state/fnm_multishells/66603_1769161758461/bin/node
    Yarn: 1.22.22 - /Users/skn0tt/.local/state/fnm_multishells/66603_1769161758461/bin/yarn
    npm: 9.9.4 - /Users/skn0tt/.local/state/fnm_multishells/66603_1769161758461/bin/npm
    pnpm: 10.28.1 - /Users/skn0tt/.local/state/fnm_multishells/66603_1769161758461/bin/pnpm
    Deno: 2.5.2 - /opt/homebrew/bin/deno
  IDEs:
    VSCode: 1.108.1 - /opt/homebrew/bin/code
    Claude Code: 2.1.15 - /opt/homebrew/bin/claude
  Languages:
    Bash: 3.2.57 - /bin/bash

Activity

  1. Skn0tt commented on Jan 23, 2026

    @Skn0tt
    ContributorAuthor

    Andrey Lushnikov (@aslushnikov) could you take a look? this seems to have regressed in the last roll.

  2. changed the title [-][Bug]: locale is not propagated to workers[/-] [+][Bug]: locale is not propagated to workers in firefox[/+] on Jan 29, 2026
  3. Torgen commented on Feb 1, 2026

    @Torgen

    I had issues with navigator.language being undefined in the latest version. Does that seem like it could be related?

  4. aslushnikov commented on Feb 4, 2026

    @aslushnikov
    Contributor

    Dan Rosart (@Torgen) this i cannot reproduce; can you please file a separate issue?

  5. aslushnikov commented on May 5, 2026

    @aslushnikov
    Contributor

    This is still not fixed upstream; I pinged Mozilla folks. If there are no plans to fix upstream, we should consider bringing back our homegrown timezone & locale implementation.

  6. aslushnikov commented on Jul 6, 2026

    @aslushnikov
    Contributor

    This will be fixed with the roll to 152.

  7. dgozman commented on Jul 22, 2026

    @dgozman
    Collaborator

    Fixed by #41938.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions