[🚀 Feature]: Implement Navigation Commands with BiDi · SeleniumHQ/selenium#13995

(4 commentaires) (1 réaction) (0 assignés)Java (8 680 forks)batch import

B-devtoolsC-dotnetC-javaC-nodejsC-pyC-rbI-enhancementgood first issue

Métriques du dépôt

Stars: (34 077 stars)
Métriques de merge PR: (Merge moyen 2j 18h) (85 PRs mergées en 30 j)

Description

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

Guide contributeur

Direction de recherche: Examinez l'implémentation BiDi existante en Java, en particulier les commandes de navigation, et suivez le modèle de l'implémentation .NET (#14052). Comprenez comment la stratégie de chargement de page affecte l'attente de navigation.
Stack technique: java
Domaine: backend
Type d'issue: Fonctionnalité
Difficulté: 3
Temps estimé: 3-5 jours
Statut d'activité: Active
Clarté: Claire
Prérequis: JavaSeleniumWebDriver BiDi
Accessibilité débutant: 30