qtwebengine | Qt WebEngine -

Just managed to find a solution, under where I had browser = QWebEngineView(), I put in an User agent:

Qt6 is a big change so for compatibility reasons Qt does not provide this module, it will be provided in Qt 6.2 as this post: Add-on support in Qt 6.0 and beyond points out.

For Qt 6.2 we are planning to provide the following additional libraries:

• Qt Bluetooth
• Qt Data Visualization
• Qt Lottie Animation
• Qt Multimedia
• Qt NFC
• Qt Positioning
• Qt Quick Dialogs: Folder, Message Box
• Qt Remote Objects
• Qt Sensors
• Qt SerialBus
• Qt SerialPort
• Qt WebChannel
• Qt WebEngine
• Qt WebSockets
• Qt WebView

_{(emphasis mine)}

So you will have to wait for that release that according to what was announced will be available for September 2021

You can add separate elements, probably elements, on either side of your input, then use CSS to position them appropriately.

As far as tick-marks are concerned, there isn't a standard way to add those. However, with the concept of progressive enhancement in mind, feel free to add the without the label attributes (since you'll have those set using the above-referenced elements) so that users who access your site on browsers that do support the tick marks can see them.

The problem with resizing the WebEngineView is that HTML will see that your device screen suddenly shrunk and may decide to present a vastly different layout, for example move menu from top to side of the screen.

Even if this has not happened, layout has changed. The position on the new "screen" does not correspond to the position on the old one, there is no 1:1 relation, which is why it scrolls to a seemingly random spot in the first place.

We can tell webpage to scroll a focused element into view of new viewport:

• If it was already onscreen than nothing happens.
• If not, webpage scrolls so that the element fits on the screen if possible. scrollIntoView has parameters to scroll to the top/bottom of the screen as desired

So when onscreen keyboard is opened:

1. Save original scrollPosition
2. Resize WebEngineView
3. Optionally assign scrollPosition to saved value - although it probably won't do you any good
4. Use runJavaScript to determine activeElement and make it scrollIntoView

Repeat same steps when onscreen keyboard is dismissed.

Another approach would be to not resize the "screen" and just scroll the element into view if it got covered.

This would require Qt to change VisualViewport while leaving LayoutViewport intact (see this and this for more information) but it seems that Qt cannot do that, at least not through QML alone.

That leaves us with having to do it manually: determine position with getBoundingClientRect, calculate how much space does keyboard cover, and if it is not inside our calculated uncovered view area - scrollTo it.

(you will still need runJavaScript to get inside the webpage)

Perhaps this and this SO questions can help

@Hazelnutek reported some success with document.activeElement.scrollIntoViewIfNeeded()

Please see discussion in comments to this answer below:

Thanks to lixinwei (https://bugreports.qt.io/browse/QTBUG-89993) the issue is resolved. Now, it successfully finds the OpenSSL and MySQL libs.

Cmake paramaters:

Looks like the implementation is done with PDFium. Qt calls FPDF_GetPageSizeByIndex and the docs state the height/width is in points.

QTextEdit since Qt 5.14 can render markdown but as the OP points out it has a limitation: it cannot render remote images. So an alternative is to use QWebEngineView + js libraries like markdown.js and marked.js as the official example shows. You can also use QNetworkAccessManager to download remote .md files.

Obviously, you are utilizing Qt Quick Compiler with release build which compiles all .qml and .js in your resources. I assume you are using qmake build system because Qt Creator enables quick compiler for qmake based release builds by default but for CMake you need to manually enable it in CMakeLists.txt (at least for now).

For qmake based build you find the answer from the Qt Quick Compiler doc:

If you have .qml or .js files which should not be compiled but just bundled by the resource system, then you can omit them from the compilation by specifying the resources files that contain them in the QTQUICK_COMPILER_SKIPPED_RESOURCES variable in your project file, like below:

You can't access Component properties, like status from there. You can only access the onCompleted signal because it's an "attached signal". I would use a Loader to track progress. Try it like this: