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

Long Press text selection Windows touch - Known CEF issue #53

Closed
tuarua opened this issue Jun 3, 2017 · 5 comments
Closed

Long Press text selection Windows touch - Known CEF issue #53

tuarua opened this issue Jun 3, 2017 · 5 comments

Comments

@tuarua
Copy link
Owner

tuarua commented Jun 3, 2017

Long pressing on text selection causes a crash on Windows 10 touch devices.
This is a bug in CEF 57.
CefSharp and indeed the CEF dist packages are released every 2nd version of Chromium.
It is currently on CEF v57 so when v59 is released it will be incorporated.
This usually occurs within a couple of weeks. 59 is due to be released sometime in June.
In the interim:
You can disable long press in under System > Pen and Touch

@tuarua tuarua added the bug label Jun 3, 2017
@tuarua tuarua self-assigned this Jun 3, 2017
@tuarua tuarua added the Win CEF label Jun 3, 2017
@salesbuddy
Copy link

Has there been any progress on this? I desperately need a fix. Even when I disable log press through Pen and Touch this happens.

@tuarua
Copy link
Owner Author

tuarua commented Oct 16, 2017

This is dependant on CefSharp.
It was a bug fixed in Chromium Embedded Framework 58
CefSharp is stuck on 57 because CEF 58 changed a fundamental part and it means it would break JS if CefSharp upgrades. It is being actively looked into by their contributors. As soon as CefSharp is updated I will update the ANE.

You can watch this ticket.
cefsharp/CefSharp#1203

@salesbuddy
Copy link

Thank you for your quick reply.

@tuarua
Copy link
Owner Author

tuarua commented Jan 22, 2018

CefSharp is soon to be updated to CEF 63 which will resolve this.
cefsharp/CefSharp#2234

@tuarua tuarua added this to the 1.3.0 milestone Feb 4, 2018
@tuarua
Copy link
Owner Author

tuarua commented Feb 8, 2018

This is now fixed in 1.3.0

@tuarua tuarua closed this as completed Feb 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants