-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Closed as not planned
Closed as not planned
Copy link
Labels
faq-able!upstreamThese issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.
Description
Is there an existing issue for this?
- I have searched both open/closed issues, no issue already exists.
CefSharp Version
126.2.70
Operating System
Windows 11
Architecture
x64
.Net Version
net 8.0
Implementation
WinForms
Reproduction Steps
- Initialize CEF with a clean CachePath on a prior version of CefSharp.WinForms.NETCore (e.g. I have tested various versions from 100.0.140-125.0.210) and either create a cookie manually or visit a site that sets a cookie.
- update to 126.2.70 and using the same CachePath the cookie is no longer available.
Expected behavior
I would have expected that the cookie created in a prior version to still be available. I have just tested the process of upgrading the following versions and each time the cookies were still intact in the next version until I hit v126.2.70.
- 100.0.140 -> 119.1.20
- 119.1.20 -> 120.1.80
- 120.1.80 -> 123.0.60
- 123.0.60 -> 124.3.80
- 124.3.80 -> 125.0.210
- 125.0.210 -> 126.2.70 *no cookies
Actual behavior
no cookies appear to be in the cookie store immediately after upgrading to v126.2.70
Regression?
yes this looks like it worked in prior versions. it appears at least since 100.0.140 the cookies have been forward compatible until we reached v126.2.70
Metadata
Metadata
Assignees
Labels
faq-able!upstreamThese issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.