Repository navigation
Conversation
limadog9
force-pushed
the
gh-114452-webbrowser-space-path
branch
from
October 20, 2026 03:57
11def8b to
bdf5db5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preserve the complete executable path when synthesizing a registered browser controller. Splitting the path on whitespace made a browser installed in a directory containing spaces fail executable lookup.
Add a regression that verifies the full path reaches executable lookup, and remove the skip that hid this problem when the Python executable itself had spaces in its path. Mock executable lookup so the regression also runs on mobile platforms that restrict executables.
Fixes #114452.
Validation:
webbrowser.Errorbefore the fix.