MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Options to use CookieManager without creating a WebView2?
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
(This is in C#/WPF context)
To get access to the CookieManager, we currently have to create WebView2 through CreateCoreWebView2ControllerAsync(windowHandle), then access it through the created object's CoreWebView2.CookieManager.
If we don't want to show the WebView2, we have to spawn a new window, hide the window, pass the window's handle to create the WebView2, and then gain access to the CookieManager.
This seems like an awkward way to access the cookie manager. Is there a way to get access to the CookieManager's functionality without the requirement for a window with WebView2's visual controls?
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 with the WebView2 creation path described in the issue, especially CreateCoreWebView2ControllerAsync(windowHandle) and CoreWebView2.CookieManager. Determine whether CookieManager can be exposed without a visual WebView2 control; done means providing a supported non-visual access path or documenting that the current hidden-window approach is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100