#55425: test: avoid launching Edge in shell.openExternal specs on Windows
Requested by John Kleinschmidt · Slack thread
Description of Change
The shell.openExternal() specs opened a local http URL in the runner's default browser, which is Edge on the Windows CI runners. Edge then made outbound connections to Google update hosts (e.g. clients2.googleusercontent.com) that the CI egress monitor flagged. On Windows the specs now register a temporary per-user URL scheme under HKCU\Software\Classes whose handler runs curl.exe against the local test server, so ShellExecute is still covered and the existing request assertion still holds, but no browser is launched. The handler ignores the opened URL, so nothing from it reaches the command line, and the key is removed after the suite. Since nothing launches Edge anymore, the afterAll that killed msedge is gone. macOS and Linux are unchanged.
Checklist
- I have filled out the PR description
- tests are changed or added
Release Notes
Notes: none
Generated by Claude Code
Backports
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron