salvadordf

The last answer of this link has the easiest solution for this case.

Thanks Peter! I only have one Delphi version per system and I didn't notice this issue.

In case there are extra problems read this.

The BPL files should be created in $(BDSCOMMONDIR)\Bpl and not in the WebView4Delphi\packages directory. Perhaps the "Package output directory" option is not set to $(BDSCOMMONDIR)\Bpl Open the Tools -> Options... menu option and then select the "Environment options -> Delphi options -> Library" node in the left tree view. There you can check the "Package output directory" value. If you can't modify that setting try adding the WebView4Delphi\packages directory to the search path.

Build WebView4DelphiVCLRTL.bpl, WebView4DelphiFMXRTL.bpl, WebView4DelphiVCL_designtime.bpl and WebView4DelphiFMX_designtime.bpl individually (in that order) or download the latest WebView4Delphi version from GitHub. I recently fixed a project order issue in the project group file thanks to the information on this thread. This Wiki article has all the details to install WebView4Delphi in Delphi.

I don't know Sciter but after reading a few things it looks similar. You should ask the WebUI developers to get a better answer but Sciter seems to have a lot more features.

I just made public the WebUI4Delphi open source project at GitHub. WebUI4Delphi is a WebUI wrapper, which allows you to use any web browser as a GUI, with Delphi in the backend and HTML5 in the frontend. WebUI doesn't embed a web browser. It just connects your Delphi application with the installed web browser using a fast protocol so you can use HTML5 as part of the GUI. WebUI4Delphi can be used in 64 bit Delphi applications for Windows. Linux and MacOS support needs testing. There are several VCL, FireMonkey and console demos. https://github.com/salvadordf/WebUI4Delphi

Yes. CEF4Delphi works on Windows, Linux and macOS. There are some unresolved issues in Linux but it works : https://github.com/salvadordf/CEF4Delphi/issues?q=is%3Aissue+is%3Aopen+label%3ALinux

FYI : I'm not a beta-tester but the latest Skia4Delphi code available at GitHub includes {$IF CompilerVersion >= 36} several times.

The WebView2 feedback repository shows similar problems. I just tried to modify the TabbedBrowser demo to create the browser while WVWindowParent1 was not visible and the browser was created correctly. The navigation events worked even while the browser wasn't visible. Perhaps Microsoft fixed this recently.

Some suggestions : Use a custom captcha when registering new users. Some forum plugins allow you to create custom questions or things like that. Don't use any version of Google recaptcha. All of them were cracked ages ago. Some forums allow you to moderate the first messages of new users. This gives you some extra work but it blocks all spammers that registered manually. Some forums have plugins that block new users that try to use known spammers IPs, email addresses, etc.

You can use these DevTools methods : Network.clearBrowserCache Storage.clearDataForOrigin If you decide to switch to WebView4Delphi then you can simply call : TWVBrowser.ClearCache TWVBrowser.ClearDataForOrigin

Try using Sikulix.

Besides the JavaScript, HTML or CSS solutions you can also use the Emulation.setScrollbarsHidden method in the DevTools protocol: https://chromedevtools.github.io/devtools-protocol/tot/Emulation/#method-setScrollbarsHidden If you use CEF4Delphi use this code : procedure TForm1.HideScrollbars; var TempParams : ICefDictionaryValue; begin try TempParams := TCefDictionaryValueRef.New; TempParams.SetBool('hidden', True); Chromium1.ExecuteDevToolsMethod(0, 'Emulation.setScrollbarsHidden', TempParams); finally TempParams := nil; end; end; If you use WebView4Delphi use this code : procedure TForm1.HideScrollbars; begin WVBrowser1.CallDevToolsProtocolMethod('Emulation.setScrollbarsHidden', '{"hidden":true}'); end;

Run the MiniBrowser demo and navigate to that web page. Then click on the top-right button and open the DevTools window. Switch to the Console tab, type your JavaScript code and press enter to read the error message : document.getElementById("linkRefresh").click(); The problem could be something as simple as a syntax error or that page could have multiple documents because it could have several frames. In any case, debugging the JavaScript code in the console tab is the best solution before calling WVBrowser.ExecuteScript