17
edits
WebDriver/RemoteProtocol/WebDriver BiDi: Difference between revisions
update m20 goal
Jdescottes (talk | contribs) (adding m20) |
Jdescottes (talk | contribs) (update m20 goal) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
== Milestones == | == Milestones == | ||
=== WebDriver BiDi Milestone 20 - In | === WebDriver BiDi Milestone 20 - In Development === | ||
'''Goal''': | '''Goal''': The priority for this milestone remains to deliver high-value items for Playwright and other clients. One of the key items will be to implement commands to start and stop screen recording. Also planned is a command to disable CSPs, as well as better widget event support for web-platform tests. In M20, we are also updating the WebDriver BiDi specifications to unblock our next implementation items. The main topics will be around support for streaming (screencasting, network responses, etc.) and WebSocket events, but there are also a variety of smaller items such as element scrolling and better download tracking. | ||
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_20|Milestone 20 status]] | '''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_20|Milestone 20 status]] | ||
=== WebDriver BiDi Milestone 19 - | === WebDriver BiDi Milestone 19 - Completed March 29th, 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. | ||