Release Notification - 81.3.x

[amaitland]

As always a big thank you to those who have contributed previously and especially those who make recurring contributions through GitHub Sponsors and BountySource Salt.

---

Release 81.3.20-pre

• Update to latest CEF build
• Create release notes
• Create cefsharp/81 release branch
• Release -pre pacakges to nuget.org

Release 81.3.x

• Resolve remaining issues attached to 81 Milestone
• Update changelog and create release notes
• Update General Usage Guide with new requirements for Cookie Persistence
• Add section to breaking changes regarding Cookie Persistence
• Generate new API Doc and upload to http://cefsharp.github.io/api/
• Release 81.3.x pacakges to nuget.org

[RealLinkers]

Is there any timeline when it would be possible to expect a full release?

[amaitland]

You can track the current progress at https://github.com/cefsharp/CefSharp/milestone/46

The issues that require code changes will need to be resolved before the first -pre release. Hopefully the final release will follow approximately two weeks after that. There is no timeline yet.

If you'd like to help out then #3106 is an easy place to start.

[amaitland]

If you'd like to help out then #3106 is an easy place to start.

This has been resolved.

CEF has updated to Chromium version 81.0.4044.138 in commit
https://bitbucket.org/chromiumembedded/cef/commits/b9282cc6f663b29e4589cdd5110da8bd88b4f0db

We should upgrade before the -pre release.

Hopefully the -pre release will be out in the next day or two.

[amaitland]

The v81.3.20-pre packages should appear on Nuget.org shortly.

[amaitland]

The MinimaleExample has been updated, use https://github.com/cefsharp/CefSharp.MinimalExample/tree/cefsharp/81 for testing purposes.

[GrabzIt]

I just cancelled my Salt sponsorship to switch over to GitHub sponsors. I am going to sign up at the end of the month.

Just wanted you to know I am not stopping my support!

[amaitland]

Just wanted you to know I am not stopping my support!

@GrabzIt Thank you for the continued support, greatly appreciated 👍 It means more now than ever, thank you!!

[amaitland]

Upgraded to CEF 81.3.10+gb223419+chromium-81.0.4044.138 relevant commit 7dc74b2

[amaitland]

Cookie persistence when using RequestContextSettings.CachePath

The encryption key used for Cookie persistence is now stored in LocalPrefs.json, this key is stored in CefSettings.RootCachePath, if you don't specify a RootCachePath then CefSettings.CachePath will be used.

When using a RequestContext you must ensure that RequestContextSettings.CachePath is equal to or a child of CefSettings.RootCachePath.

All CefSettings.CachePath and RequestContextSettings.CachePath must be equal to or a child directory of CefSettings.RootCachePath. In versions prior to 81 this wasn't strictly enforced

If non-empty this must be either equal to or a child directory of CefSettings.RootCachePath

As per RequestContextSettings.CachePath this has been a stated requirement though in versions prior to 81 this wasn't strictly enforced. Cookies won't be persisted to disk if RequestContextSettings.CachePath is a folder outside the shared root.

If a cache_path is specified local_state will now be persisted to a LocalPrefs.json file. This is necessary because local_state is used to store the cookie encryption key on Windows.

As per https://bitbucket.org/chromiumembedded/cef/issues/2890/all-the-cookies-are-deleted-automatically#comment-56757287

Further details in https://bitbucket.org/chromiumembedded/cef/issues/2890/all-the-cookies-are-deleted-automatically

Typically, only a user with the same logon credential as the user who encrypted the data can decrypt the data. In addition, the encryption and decryption usually must be done on the same computer.

As per https://magpcss.org/ceforum/viewtopic.php?f=6&t=17569#p45485

• It's no longer possible to move the cache between machines as cookies cannot be decrypted.
• Users on the same machine will likely need to have their own Cache (same as in Chrome).