-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
nuget version out of date #2158
Comments
Particular interest in upgrading to Chrome v60+ is its headless mode. As people start migrating their HTML automated tests on top of libraries integrating with headless, like puppeteer, we'd rather our test environment reflected the actual runtime environment. With CEF still running on Chrome v57, tests running on headless Chrome will lag quite behind and may produce incorrect results. |
#1203 Is currently preventing a release of newer version(s) |
We have a POC that works, but will take quite a while to get it released |
@mihailik Please keep in mind that CefSharp is maintained by a group of volunteers and individuals. There is no large company backing this project. Trust us: if it would just be a matter of "pressing a button", CefSharp 60.0.0 and 62.0.0 would already have been out. But this is not the case. It takes a lot of hard work. Some of it has been done in #2203 now; the road map can be found in #2200. (Side note: Electron is still on Chromium 58, even though it is backed by a large company - GitHub. So, if they still haven't been able to upgrade their code base, it's not realistic to expect CefSharp to go faster than them.) I will close this now, since #2200 tracks the upgrade work. Let's continue the discussion there if needed. |
Currently CefSharp packages in nuget are 6 month old, and 4 major version out of date with the official Chrome.
https://www.nuget.org/packages/CefSharp.WPF/
https://www.nuget.org/packages/CefSharp.Common/
In practice that means several major features are missing or incomplete: CSS Grid, FlexBox etc. Is there a roadmap to CEF/version update please?
The text was updated successfully, but these errors were encountered: