Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Qt 6.4 web inspector
Forum Updated to NodeBB v4.3 + New Features

Qt 6.4 web inspector

Scheduled Pinned Locked Moved Solved QtWebEngine
4 Posts 2 Posters 1.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    steno
    wrote on last edited by
    #1

    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?

    JKSHJ 1 Reply Last reply
    0
    • S steno

      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?

      JKSHJ Offline
      JKSHJ Offline
      JKSH
      Moderators
      wrote on last edited by
      #2

      @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>

      Qt Doc Search for browsers: forum.qt.io/topic/35616/web-browser-extension-for-improved-doc-searches

      1 Reply Last reply
      0
      • S Offline
        S Offline
        steno
        wrote on last edited by steno
        #3

        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.

        1 Reply Last reply
        0
        • S Offline
          S Offline
          steno
          wrote on last edited by
          #4

          Bug has been logged. https://bugreports.qt.io/browse/QTBUG-107502

          1 Reply Last reply
          1

          • Login

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups
          • Search
          • Get Qt Extensions
          • Unsolved