[Bug]: TimezoneId is not applied to service workers

Abierto
  • ¿Algo no está bien?
#43,983 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
64/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, playwright, typescript
Área
backend, testing-qa

Línea de trabajo

Read packages/playwright-core/src/server/chromium/crPage.ts around the timezone setup and compare it with service worker startup in packages/playwright-core/src/server/chromium/crServiceWorker.ts. Start by reproducing the issue with the linked minimal test, then find or add a regression test covering a worker started without an open page. Done when the worker uses the configured timezoneId from its first statement and the regression test passes.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Version

1.65.0 (latest release tested)

Steps to reproduce

Minimal reproduction, using only Playwright and a minimal Manifest V3 extension.

git clone --branch service-worker-timezone --single-branch https://github.com/vitalets/playwright-issues.git
cd playwright-issues
npm ci
npx playwright install chromium
# Adjust timezoneId in test/timezone.spec.ts if needed.
npm test

Choose a timezoneId different from your system timezone. The example uses Europe/Madrid; if your system already uses Madrid, change the timezoneId variable in test/timezone.spec.ts to Asia/Tokyo (no other changes are needed). Matching timezones mask the bug.

The test verifies the configured timezone in an ordinary page, then loads an extension whose first statement records its worker's timezone and parses 2030-01-01T23:00. No extension page is opened, and no timezone environment variable is set.

Expected behavior

The service worker uses the configured timezoneId from its first statement. Its timezone and parsed date match the page's values.

Actual behavior

The page uses the configured timezone, but the worker retains the system timezone. On my Madrid-configured machine, changing the example to Asia/Tokyo produces:

- "timezone": "Asia/Tokyo"
+ "timezone": "Europe/Madrid"
- "localDate": "2030-01-01T14:00:00.000Z"
+ "localDate": "2030-01-01T22:00:00.000Z"
Additional context

Reproduced with bundled Chromium 158.0.8127.18 on macOS. No clock mocking or third-party helpers are involved.

Both web extensions and regular websites are affected:

  • Web extension: the linked reproduction loads an extension without opening an extension page. Its worker starts with the system timezone instead of the configured timezone.
  • Regular website: in a separate local experiment, I registered a service worker, closed the persistent browser context, reopened the same profile with the same timezone setting, and started the registered worker using CDP ServiceWorker.startWorker, without reopening the site. Its first statement also recorded the browser default timezone instead of the configured timezone.

Initial registration while the website page was open used Madrid correctly. An open page can mask the problem when its timezone override affects the worker's shared renderer process.

Page initialization applies the context's timezoneId, while service-worker initialization resumes execution without applying it.

Environment

Relevant output from npx envinfo --preset playwright:

System:
  OS: macOS 26.6.2
  CPU: (10) arm64 Apple M1 Pro
Binaries:
  Node: 24.16.0
  npm: 11.21.1
npmPackages:
  @playwright/test: 1.65.0 => 1.65.0
Lenguaje dominante
TypeScript
Estrellas
99.1k
Forks
6.8k
Merge medio
17 h 6 min
PR fusionados (30 d)
306

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/playwright

Todos los issues de microsoft/playwright

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.