WebDriver Bidi does not emulate timezone in dedicated and shared workers
Categories
(Remote Protocol :: WebDriver BiDi, defect, P2)
Tracking
(firefox153 fixed)
| Tracking | Status | |
|---|---|---|
| firefox153 | --- | fixed |
People
(Reporter: aslushnikov, Assigned: Sasha)
References
(Blocks 1 open bug)
Details
(Whiteboard: [webdriver:m20][wptsync upstream][webdriver:relnote])
Attachments
(2 files)
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:
- clone playwright repo: git clone https://github.com/microsoft/playwright
- remove the line #120 in
tests/library/browsercontext-timezone-id.spec.ts- theit.failexpectation. - 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.
| Assignee | ||
Comment 1•5 months ago
|
||
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.
Updated•5 months ago
|
Updated•4 months ago
|
| Assignee | ||
Updated•4 months ago
|
| Reporter | ||
Comment 2•2 months ago
|
||
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•2 months ago
|
||
(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.
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 4•2 months ago
|
||
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.
| Reporter | ||
Comment 5•2 months ago
|
||
Yes, we only had it in dedicated workers, so this would be enough.
| Assignee | ||
Updated•2 months ago
|
| Assignee | ||
Comment 6•2 months ago
|
||
| Assignee | ||
Comment 7•2 months ago
|
||
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/60562 for changes under testing/web-platform/tests
Comment 10•1 month ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/0c05f1603719
https://hg.mozilla.org/mozilla-central/rev/51f2c32e3536
Upstream PR merged by moz-wptsync-bot
Description
•