Qt 6.4 web inspector
-
wrote on 3 Oct 2022, 15:59 last edited by
I can't find anything that says something has changed with Qt 6.4 in regards to debugging the webengine with chrome's web inspector. I pass in --remote-debugging-port=<port_number> as a command line argument, but it doesn't show the page like previous versions of Qt. Has anyone else seen this?
-
I can't find anything that says something has changed with Qt 6.4 in regards to debugging the webengine with chrome's web inspector. I pass in --remote-debugging-port=<port_number> as a command line argument, but it doesn't show the page like previous versions of Qt. Has anyone else seen this?
@steno said in Qt 6.4 web inspector:
I can't find anything that says something has changed with Qt 6.4 in regards to debugging the webengine with chrome's web inspector. I pass in --remote-debugging-port=<port_number> as a command line argument, but it doesn't show the page like previous versions of Qt. Has anyone else seen this?
I can't see anything that has changed; the documentation for Qt 6.4 and Qt 5.15 show the same: https://doc.qt.io/qt-6/qtwebengine-debugging.html#qt-webengine-developer-tools
Anyway, you can open another Chromium-based browser (like Google Chrome or Microsoft Edge) and open
http://localhost:<port_number> -
wrote on 4 Oct 2022, 13:08 last edited by steno 10 Apr 2022, 13:09
That's what I'm talking about. I can target 6.3.2 in Creator and I can inspect the JS in chrome. As soon as I change the target to 6.4, I can't inspect anything in chrome. It works in one case and then the other case it says connection refused.
-
wrote on 10 Oct 2022, 14:26 last edited by
Bug has been logged. https://bugreports.qt.io/browse/QTBUG-107502
1/4