Similarly for MacOS. It is a few code on Objective-C, for call Native API, for create and use the control. ---
I repeat, forget about QtWebEngine, QtWebKit and everything that is connected with them, them will never work normally.
Advantages of a "Native WebView", on updated OS -- No problems with websites! Microsoft and Apple are interested in it, they have resources and influence for this purpose.
For Windows: Need use ActiveX control, with the API provided by the Active Qt module.
The QAxContainer module is a static library implementing QObject and QWidget subclasses, QAxObject and QAxWidget, that act as containers for COM objects and ActiveX controls.
"Qt WebView" will always have problems (also as well as WebKit, CEF).
Many users need no extensions of the browser, they can do without advertizing blocking. At the same time none of them will use the buggy browser which can't open the necessary website. Win10 and MacOS are the updated OS, which it seems provide relevant "Native WebView". ---
Survival of the project requires two things:
1) To provide "Native WebView" for Win10 and MacOS. It is necessary to take users, there where they are!
2) To make a fork of any open mobile (Android/iOS) browser (Firefox/Chrome), and to name it "Otter Mobile". At the same time to add exchange of files of bookmarks and a session, through the file (Desktop-Mobile). This is enough to do.
Instead of being wasted, for compiling "Otter Desktop" every week, it is better to compile "Otter Mobile" once. --- Forget about Qt, deal with "Native WebView" and Mobile App. Increase in users who have no problems will give you new motivation and the chance of monetization.
