WebDriver/RemoteProtocol/WebDriver BiDi: Difference between revisions

Jump to navigation Jump to search
Complete milestone 17
(→‎Milestones: Add milestone 18)
(Complete milestone 17)
Line 6: Line 6:
== Milestones ==
== Milestones ==


=== WebDriver BiDi Milestone 18 - In Planning ===
=== WebDriver BiDi Milestone 18 - In Development ===
'''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.


'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_18|Milestone 18 status]]
'''Details''': [[WebDriver/RemoteProtocol/WebDriver_BiDi/Milestone_18|Milestone 18 status]]


=== WebDriver BiDi Milestone 17 - In Development ===
=== WebDriver BiDi Milestone 17 - Completed September 26th, 2025 ===
'''Goal''': In this milestone, we are expanding WebDriver BiDi’s emulation features to make it easier to simulate locales, timezones, mobile devices etc. We are also adding support for retrieving network response bodies, which has been strongly requested by clients. Those features benefit existing WebDriver BiDi clients, and are also key requirements for Playwright adoption. Internally we keep supporting Desktop Test Engineering by improving our support for chrome privileged script evaluation and widget-level events.
'''Goal''': In this milestone, we are expanding WebDriver BiDi’s emulation features to make it easier to simulate locales, timezones, mobile devices etc. We are also adding support for retrieving network response bodies, which has been strongly requested by clients. Those features benefit existing WebDriver BiDi clients, and are also key requirements for Playwright adoption. Internally we keep supporting Desktop Test Engineering by improving our support for chrome privileged script evaluation and widget-level events.


6

edits

Navigation menu