Skip to content

selenium_jspi: don't pass experimental flag with chrome >= 137#167

Open
hoodmane wants to merge 4 commits into
pyodide:mainfrom
hoodmane:jspi-chrome-137
Open

selenium_jspi: don't pass experimental flag with chrome >= 137#167
hoodmane wants to merge 4 commits into
pyodide:mainfrom
hoodmane:jspi-chrome-137

Conversation

@hoodmane

Copy link
Copy Markdown
Member

JSPI is enabled by default in this case.

Resolves #163.

JSPI is enabled by default in this case
@hoodmane hoodmane changed the title selenium_jspi: don't pass experimental flag with chrome > 137 selenium_jspi: don't pass experimental flag with chrome >= 137 Jul 21, 2025
Comment thread pytest_pyodide/runner.py
Comment on lines +452 to +456
driver = Chrome(options=options)
chrome_version = int(
driver.capabilities.get("browserVersion", "0").split(".")[0]
)
driver.quit()

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am curious how expensive it is to initialize a Chrome instance here. If it actually runs a new Chrome browser, it would be nice if we can cache the value somewhere instead of calling it everytime in get_driver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Script timeout in Chrome Canary with selenium_jspi fixture

2 participants