Cookies read/write not working in WebView on WinUI

[chrfin]

Description

Reading or writing Cookies (see docs) are not working on WinUI.
I think this is because the WebViewRenderer uses the "old" HttpBaseProtocolFilter approach to read/write cookies to the underlying WebView2 control, which does not work.
The new approach should be used: https://github.com/MicrosoftEdge/WebView2Feedback/blob/master/specs/CookieManagement.md

Steps to Reproduce

See https://github.com/dotnet/maui/blob/main/src/Compatibility/Core/src/Windows/WebViewRenderer.cs#L255

Version with bug

Preview 11

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

10.0.19041

Did you find any workaround?

I'm using a custom HybridWebView where I (partially) implemented the new solution.
See devsmadeofsteel/Plugin.HybridWebView#17

Relevant log output

No response

[chrfin]

I may try to update the MAUI WebViewRenderer myself and create a pull request if I find some time later this week.

[wenwen60]

Thank you so much for your bug report! Unfortunately, we cannot reproduce your issue with the information above, could you provide a sample project/screenshots or more details that we can reproduce your issue? That should greatly speed up the process, thanks!

[ghost]

Hi @chrfin. We have added the "s/needs-repro" label to this issue, which indicates that we require steps and sample code to reproduce the issue before we can take further action. Please try to create a minimal sample project/solution or code samples which reproduce the issue, ideally as a GitHub repo that we can clone. See more details about creating repros here: https://github.com/dotnet/maui/blob/main/.github/repro.md

This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[chrfin]

@wenwen60 The renderer for MAUI still uses HttpBaseProtocolFilter (see link above), but for WebView2 the new CookieManager  should be used (see other link above).

[VincentBu]

Here is a sample project: MauiApp3901.zip

feel free to point out if the following repro steps doesn't make sense:

1. run the project
2. press F12 to open DevTools
3. click button "WriteCookie"
4. check cookie in DevTools and there is no cookie we write
   

[alexeystrakh]

I'm having the same issue with cookies are not being set on MAUI WebView control. I have created a sample to reproduce the issue: https://github.com/xamcat/maui-webview-cookieissue

Maui WebView:

WinUI3 WebView2

The sample contains two projects:

1. Maui WebView - cookie is set and NOT visible to JS code
2. WinUI3 WebView2 - cookie is set and visible to the JS code

[jfversluis]

I see that we merged a PR that uses the CookieManager: https://github.com/dotnet/maui/blob/main/src/Core/src/Handlers/WebView/WebViewHandler.Windows.cs#L169

Could someone confirm that this is still an issue with the latest release (6.0.400, released yesterday at the time of writing)

[ghost]

Hi @chrfin. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[Banurega]

I see that we merged a PR that uses the CookieManager: https://github.com/dotnet/maui/blob/main/src/Core/src/Handlers/WebView/WebViewHandler.Windows.cs#L169

Could someone confirm that this is still an issue with the latest release (6.0.400, released yesterday at the time of writing)

Hi, I'm still having the same issue with cookies are not set on MAUI WebView after release.

[degenet]

I see that we merged a PR that uses the CookieManager: https://github.com/dotnet/maui/blob/main/src/Core/src/Handlers/WebView/WebViewHandler.Windows.cs#L169

Could someone confirm that this is still an issue with the latest release (6.0.400, released yesterday at the time of writing)

I can confirm this issue is still present.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.