MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Read live HTML content of displayed webpage
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Can WebView2 support something like WebView.CaptureSelectedContentToDataPackageAsync but with an additional option to choose whether it captures the entire webpage versus only the selected portion of the webpage? For troubleshooting purposes, we would find it useful to be able to capture and analyze the HTML of the entire webpage, in order to figure out what's going wrong when a malfunction is reported by users.
I do realize that I can directly download the URL by myself using Windows.Web.Http.HttpClient but that's not the same thing because that effectively downloads the "source code" instead of the current live content of the webpage. JavaScript in the webpage is capable of making many modifications to the webpage, thus there can be a big difference between what HttpClient obtains and what is actually displayed in the WebView2.
Ofcourse the original intention of CaptureSelectedContentToDataPackageAsync is to support copy & paste scenarios, and this is also a valid usage of this feature. If this feature is already supported for capturing the selected portion of the page, then it seems like very little work to create an option to make it capture the entire page.
I think some other issues are much higher priority than this issue, but this feature would still be useful, even if it's not the most important thing currently.
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 reviewing WebView.CaptureSelectedContentToDataPackageAsync and the WebView2 live-page behavior described in the issue, then compare it with Windows.Web.Http.HttpClient. No repository file, test, or entry point is named; done means determining whether whole-page live HTML capture is supported and identifying the API or design needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100