17
edits
WebDriver/RemoteProtocol/WebDriver BiDi: Difference between revisions
WebDriver/RemoteProtocol/WebDriver BiDi (view source)
Revision as of 18:13, 24 March 2026
, 24 Marchadding m20
(M19 description) |
Jdescottes (talk | contribs) (adding m20) |
||
| Line 6: | Line 6: | ||
== Milestones == | == Milestones == | ||
=== WebDriver BiDi Milestone 19 - In Development, | === WebDriver BiDi Milestone 20 - In planning, 2026 === | ||
'''Goal''': TBD. | |||
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_20|Milestone 20 status]] | |||
=== WebDriver BiDi Milestone 19 - In Development, 2026 === | |||
'''Goal''': This milestone will focus on delivering high-priority APIs required for experimental WebDriver BiDi support in Playwright, including capabilities such as CSP bypass, correctly applying user context configurations when invoking `window.open`. In parallel, we will enable widget-level touch event support for web-platform tests and continue evolving the BiDi framework to properly support chrome browsing contexts and workers. This work is foundational for future use cases, including controlling Firefox via MCP servers. | '''Goal''': This milestone will focus on delivering high-priority APIs required for experimental WebDriver BiDi support in Playwright, including capabilities such as CSP bypass, correctly applying user context configurations when invoking `window.open`. In parallel, we will enable widget-level touch event support for web-platform tests and continue evolving the BiDi framework to properly support chrome browsing contexts and workers. This work is foundational for future use cases, including controlling Firefox via MCP servers. | ||
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_19|Milestone 19 status]] | '''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_19|Milestone 19 status]] | ||
=== WebDriver BiDi Milestone 18 - Completed January 4th, | === WebDriver BiDi Milestone 18 - Completed January 4th, 2026 === | ||
'''Goal''': This milestone will maintain focus on APIs required for Playwright adoption such as touch, device screen dimensions and locale emulations, network request body collection and more. Also, we will further work on support for chrome privileged script evaluation and widget-level events to help the Desktop Test Engineering team. | '''Goal''': This milestone will maintain focus on APIs required for Playwright adoption such as touch, device screen dimensions and locale emulations, network request body collection and more. Also, we will further work on support for chrome privileged script evaluation and widget-level events to help the Desktop Test Engineering team. | ||