SeleniumHQ/selenium

[🚀 Feature]: Implement Navigation Commands with BiDi

Open

#13,995 创建于 2024年5月21日

在 GitHub 查看
 (3 评论) (1 反应) (0 负责人)Java (34,077 star) (8,680 fork)batch import
B-devtoolsC-dotnetC-javaC-nodejsC-pyC-rbI-enhancementgood first issue

描述

Feature and motivation

Moving forward, Selenium plans to update implementations to use WebDriver BiDi instead of WebDriver Classic if BiDi is enabled.

It was decided at the Selenium Dev Summit that we would implement the navigation commands with BiDi in all the bindings as the minimum for Selenium 5. This will act as a proof of concept that a user can successfully use either BiDi or Classic depending on the capabilities that are set. We do not need to implement everything in BiDi spec before releasing Selenium 5, just have a working module as a pattern to work from.

Considerations

  • let's not worry about making sure we're storing the browser context id properly everywhere for this issue
  • we do need to make sure we're looking at the user's page load strategy to determine how to wait for the navigation

Implementations

  • .NET — #14052

贡献者指南

技术栈
javacsharp
领域
api
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Understanding of WebDriver BiDi specificationFamiliarity with Selenium's architecture
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
The .NET implementation is already in progress (#14052). For other bindings, developers should review the BiDi specification for navigation commands and follow the pattern established in the .NET PR. The implementation must consider the user's page load strategy for waiting. The browser context ID storage is not a priority. Focus on making the navigation work with BiDi when enabled.