Skip to content

[🚀 Feature]: Document enableExtensionTargets flag in Chrome implicitly when using Extension Targets #2410

@Delta456

Description

@Delta456

Description

Since ChromeDriverv136, the capability enableExtensionTargets needs to be set when using Extension Targets.

We need to document this for all bindings

To know why this change happened, check here

Have you considered any alternatives or workarounds?

It is now a common issue. SeleniumHQ/selenium#15685 and SeleniumHQ/selenium#15993 are such examples. I see no alternative for this.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions