Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Notification - 81.3.x #3111

Closed
10 tasks done
amaitland opened this issue Apr 27, 2020 · 12 comments
Closed
10 tasks done

Release Notification - 81.3.x #3111

amaitland opened this issue Apr 27, 2020 · 12 comments
Assignees
Milestone

Comments

@amaitland
Copy link
Member

amaitland commented Apr 27, 2020

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

@amaitland amaitland added this to the 81.0.0 milestone Apr 27, 2020
@amaitland amaitland self-assigned this Apr 27, 2020
@amaitland amaitland changed the title Release Notification - vNext Release Notification - 81.2.x Apr 28, 2020
@RealLinkers
Copy link

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

@amaitland amaitland pinned this issue May 1, 2020
@amaitland
Copy link
Member Author

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 amaitland changed the title Release Notification - 81.2.x Release Notification - 81.3.x May 3, 2020
@amaitland
Copy link
Member Author

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
Copy link
Member Author

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

@amaitland
Copy link
Member Author

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

@GrabzIt
Copy link
Contributor

GrabzIt commented May 11, 2020

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
Copy link
Member Author

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
Copy link
Member Author

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

@amaitland
Copy link
Member Author

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).

@amaitland
Copy link
Member Author

I'm waiting on a response for #3120 (which I'm unable to reproduce). Depending on the response (and any further issues that are raised in the next day or two) I'll hopefully release the stable version to Nuget.org in 2-3 days.

@amaitland
Copy link
Member Author

The packages have been pushed to Nuget.org and should appear shortly.

@KairoMartins18

This comment has been minimized.

@cefsharp cefsharp locked as resolved and limited conversation to collaborators Sep 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants