MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Feature]: Unable to open port using startup parameters 150.0.4078.65
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Describe the feature/enhancement you need
I need to use remote debugging functionality. 149.0.4022.98 works, but 150.0.4078.65 cannot open the port using the startup parameters --remote-debugging-port=9222 --remote-debugging-address=0.0.0.0.
The scenario/use case where you would use this feature
Remote development and debugging when unable to go to the server room
How important is this request to you?
Impactful. My app's user experience would be significantly compromised without it.
Suggested implementation
No response
What does your app do? Is there a pending deadline for this request?
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior in WebView2 150.0.4078.65 with --remote-debugging-port=9222 and --remote-debugging-address=0.0.0.0, then compare it with 149.0.4022.98. Determine whether the port can be opened reliably for remote development and debugging, and document the cause or required product change.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100