FWIW, the WebBrowser control (IE) works pretty well - *if* you configure it for your application so it's using IE 11 which gives you HTML5/CSS3 etc. If you just use the default without config, you get IE7 which doesn't work for most things you actually want to do.

I use the Web Browser control for sophisticated integrations in a number of commercial applications and it works with all but the latest JavaScript (no ES2015+ support). There are still quirks mainly related to focus management but you'll have that with just about any ActiveX control in VFP.

And for FoxPro it's probably the most stable solution as ActiveX integration into VFP is tricky and adding something as complex as Chromium/CEF and making that reliable is tricky at best.

Here's a blog post that talks about how to configure your application to use the latest version of IE:
Web Browser Control & Specifying the IE Version


+++ Rick ---

>Hi all,
>
>Just out of curiousity, has anyone tested this chromium-based activeX from within VFP - or VB6.
>
>Looks like a lousy proposition. But there are worse ones to-day in this style. And I'd still be glad to incrementally improve parts of our WIN32 VFP-based GUIs.
>
>I never tried MS-browser-based solutions from VFP. But rendering a few bits with an embedded chrome engine does not look like nonsense. Except possibly for RAM and download cost of course:-) I am not looking for http communication. Just GUI bits.
>
>Be glad to hear about feedback from UT members!
>
>Daniel.