fix: escape URL passed to shell.openExternal on windows #28334
Merged
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.
This aligns our
openExternal
behavior with upstream where the URL should be escaped before being sent to the external handler. Most applications expect a spec-compliant URI, this ensures they receive one.Notes: URLS passed to
shell.openExternal
on windows are now correctly URI encoded. This was already occurring on macOS and Linux.