BiDi+ commands are not aligned with the spec #2757
Labels
Comments
|
Proposed solution: http://go/webdriver:bidi-plus-naming |
Lightning00Blade
changed the title
This was referenced Nov 28, 2024
|
@sadym-chromium I want to work on this issue .Please assign me |
This is an umbrella issue. Please choose a specific issue you plan to work on. |
|
Thank you @sadym-chromium for letting me know |
aarongable
pushed a commit
to chromium/chromium
that referenced
this issue
Jan 22, 2025
Use proper named custom WebDriver BiDi properties with `goog:` prefix. GoogleChromeLabs/chromium-bidi#2757 Breaking change: legacy BiDi `channel` property is not allowed anymore. Change-Id: Ib551008ccac59196362ed1899a0e222ef72f6a7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6179410 Commit-Queue: Maksim Sadym <[email protected]> Reviewed-by: Alex Rudenko <[email protected]> Reviewed-by: Maksim Sadym <[email protected]> Cr-Commit-Position: refs/heads/main@{#1409612}
T3-M4
pushed a commit
to bayandin/chromedriver
that referenced
this issue
Jan 23, 2025
Use proper named custom WebDriver BiDi properties with `goog:` prefix. GoogleChromeLabs/chromium-bidi#2757 Breaking change: legacy BiDi `channel` property is not allowed anymore. Change-Id: Ib551008ccac59196362ed1899a0e222ef72f6a7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6179410 Commit-Queue: Maksim Sadym <[email protected]> Reviewed-by: Alex Rudenko <[email protected]> Reviewed-by: Maksim Sadym <[email protected]> Cr-Commit-Position: refs/heads/main@{#1409612}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WebDriver BiDi specification restricts vendor-specific extension modules to have a prefix, in case of Chromium it's
goog:. Currently, BiDi+ don't have that prefixes, which makes the implementation not spec compliant.The text was updated successfully, but these errors were encountered: