Hi,
1. Is it correct, that the WebEngine runs with “Mozilla/5.0, Chrome/56.0.2924.122, …” from 2016?
2. If yes, is it possible to replace it manually with a newer version?
3. If not, which Chrome Version runs in the latest build of VRED?
Thanks in advance!
We are using the qtwebengine that comes with Qt. VRED is currently using Qt 5.12.6 wich is using Chromium 69. Keep this in mind when using features/css styling etc. that were introduced with a newer Chrom version and look different in your browser compare to what you see in VRED.
Vred2019.2 UserAgent:
Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.9.5 Chrome/56.0.2924.122 Safari/537.36
Vred2020.3 UserAgent:
Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.12.3 Chrome/69.0.3497.128 Safari/537.36
I know, this is very specific, but ...
The QT Webengine supports access to its internal Chromium Flags (@see https://doc.qt.io/qt-5/qtwebengine-debugging.html, https://myprogrammingnotes.com/pass-parameters-ch...).
Is it possible to achieve this in VRED too? Do we have access to the instance of the Webengine via script?
Hi,
by a quick search i've found the modules vrWebEngineObj and vrWebOverlay
vrWebEngineObj sounds promising but there is not much. No class only these methods.
vrWebOverlay has a class, a constructor and inherits from some baseclasses. But nothing in you are looking for.
Best reagards
Unfortunately we currenly do not yet have a generic scripting interface for WebEngines.
The environment variables from https://doc.qt.io/qt-5/qtwebengine-debugging.html should work. We're not doing anything to prevent that. I just tested with QTWEBENGINE_REMOTE_DEBUGGING and was able to debug the website displayed in a frontplate by connecting from Chrome to the specified port.
Hi Markus,
Thank you. This sounds promising. We'll take a look.
Best regards
Can't find what you're looking for? Ask the community or share your knowledge.