Update to CEF 77.1.14

[dilfich]

Please, remember that I'm just an independent developer. I don't work for Google or any other corporation.

I have nothing against you, thank you so much for all the work that has been done.

Registering an scheme is not a simple solution but it's the best thing we have to avoid these problems and other limitations imposed by Chromium for security reasons. It's also the solution for some problems using LoadURL with a FILE:// URL

Prompt me then, CefGetDataURI works, with loading of the text of a problem is not present, but how to specify the address as it was at LoadString?
The example I showed so does not work because there is no site address, I'm just stumped.
devtools
initiator - data:text/html;charset=utf-8;base64,PHNjcm
and for normal work it is necessary that there initiator was a site address.

[salvadordf]

We've just updated 76.1.13 -> 77.1.14
And most of our http requests stopped working with net::ERR_TUNNEL_CONNECTION_FAILED
Our source is competely same as for 76.1.13
What did we missed?

I tested several HTTP, SOCKS4 and SOCKS5 free proxies in the MiniBrowser demo and they worked.

There are many web pages with suggestions to fix that error in Chrome. They say that it can be fixed by doing this :

• Delete the cache directory used by CEF.
• Reset your TCP/IP and flush your DNS. Read this to know how : https://troubleshooter.xyz/wiki/fix-err ... le-chrome/

[salvadordf]

Prompt me then, CefGetDataURI works, with loading of the text of a problem is not present, but how to specify the address as it was at LoadString?
The example I showed so does not work because there is no site address, I'm just stumped.
devtools
initiator - data:text/html;charset=utf-8;base64,PHNjcm
and for normal work it is necessary that there initiator was a site address.

As far as I know, LoadURL can't load a DATA URL and make the browser think that it comes from a certain domain.

I don't have much experience injecting JavaScript but perhaps these properties are useful in this case :

• GlobalCEFApp.DisableWebSecurity : Don't enforce the same-origin policy.
• GlobalCEFApp.AllowRunningInsecureContent : Allow https pages to run JavaScript, CSS or plugins from http URLs.

You need to set these properties before the GlobalCEFApp.StartMainProcess call in the DPR file.

Have you tried loading a web page and then executing some JavaScript code that adds the "<script>" and "<div>" elements you mentioned before to the loaded document?

[dilfich]

No, none of this solves the problem. How bad, even with the crash can be reconciled, but this is an irreplaceable minus. How many did not look, and did not understand for what reason it broke after at least 40 versions, it seems to me if there was a problem that that would be done earlier. I want to believe that broke by mistake.