SeleniumHQ/seleniumhq.github.io

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

Open

#2,410 opened on Jul 4, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)HTML (1,015 forks)batch import
I-enhancementhacktoberfest

Repository metrics

Stars
 (712 stars)
PR merge metrics
 (Avg merge 2d 4h) (8 merged PRs in 30d)

Description

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. https://github.com/SeleniumHQ/selenium/issues/15685 and https://github.com/SeleniumHQ/selenium/issues/15993 are such examples. I see no alternative for this.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.