Hi all,
Starting in ChromeDriver 136, introspecting Chrome Extension targets (chrome-extension:// URLs and MV2 background_pages) will require enabling the enableExtensionTargets capability.
This change was introduced to provide better separation between regular web application testing and Chrome Extension testing, and would help mitigate regressions occurring due to extension targets being exposed as part of regular target introspection (including Chrome internal features using extension targets).
As an example of how to use this new capability that’s exposed as a ChromeOption, I’ve put together a Selenium-Node example and the ChromeDriver integration suite has more Python examples.
--
Thanks,
Alex