MicrosoftEdge / MicrosoftEdge/WebView2Feedback

WebView2WebView->Navigate requires full URL?

Open
#94 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug doc priority-low tracked
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

It seems in the sample and in my own code when calling WebView2WebView->Navigate the URL must be a full URL such as "https://www.whatismybrowser.com". If you specify a string like "www.whatismybrowser.com" the function fails with an invalid arguments error. In the WebBrowser control you can specify any sort of string for the URL and the control parses and resolves it correctly.

Will the release version add this partial URL resolve functionality to WebView2WebView->Navigate?
Without this it is a severe drawback to existing code where the WebBrowser IE control works easily.

AB#28586569

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at WebView2WebView->Navigate and reproduce the difference between a full URL and a string such as "www.whatismybrowser.com". Compare the expected behavior with the existing WebBrowser control; done means determining whether partial URL resolution is supported and documenting the outcome or required release behavior.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.