2015657 - WebDriver Bidi does not emulate timezone in dedicated and shared workers

Status: ASSIGNED

(Remote Protocol :: WebDriver BiDi, defect, P2)

Description

[Andrey Lushnikov]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36

Steps to reproduce:

• Downstream Playwright bug: https://github.com/microsoft/playwright/issues/38919
• Downstream playwright test: https://github.com/microsoft/playwright/blob/d91dce9170eeec4de22ed4731dce25b26b58c29f/tests/library/browsercontext-timezone-id.spec.ts#L119

Reproduction:

1. clone playwright repo: git clone https://github.com/microsoft/playwright
2. remove the line #120 in tests/library/browsercontext-timezone-id.spec.ts - the it.fail expectation.
3. Run the test with Firefox Bidi: npm run biditest browsercontext-timezone-id:119 -- --project moz-firefox-nightly-library

Actual results:

The test fails because WebDriver bidi does not emulate timezone in workers.

Expected results:

WebDriver should emulate timezone in workers. The test should pass.

Comment 1

[Alexandra Borovova [:Sasha]]

For timezone emulation to be picked up by the workers, we have to implement the logic of updating the timezone in the realm of the existing and new workers.

Comment 2

[Andrey Lushnikov]

Hi folks,

Are there any plans on fixing this? If not, we'll consider migrating away from BiDi-powered api for timezone emulation back to the Juggler home-grown implementation.

Comment 3

[Julian Descottes [:jdescottes]]

(In reply to Andrey Lushnikov from comment #2)

Hi folks,

Are there any plans on fixing this? If not, we'll consider migrating away from BiDi-powered api for timezone emulation back to the Juggler home-grown implementation.

This bug is in the current milestone, which spans until end of June.
It's only P3, but I think :sasha wanted to pick this up, so there's a good chance that it gets resolved before end of June.

Comment 4

[Alexandra Borovova [:Sasha]]

Hey Andrey,

How critical for you is the support of timezone override in service workers? Since service workers can belong to multiple browsing contexts, it's harder to architect. So I think to speed up things, we could consider moving it to follow-up and introduce in the scope of this bug only the support for dedicated and shared workers. Let me know what you think.

Comment 5

[Andrey Lushnikov]

Yes, we only had it in dedicated workers, so this would be enough.

Comment 6

[Alexandra Borovova [:Sasha]]

Attachment: Bug 2015657 - Override timezone in web and shared workers when "browsingContext.timezoneOverride" is set in related browsing contexts.

Comment 7

[Alexandra Borovova [:Sasha]]

Attachment: Bug 2015657 - [wdspec] Add tests for overriding timezone with "emulation.setTimezoneOverride" in workers.