Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for WebAssembly
  4. Two major problem that prevent QT webassembly used in real project.
Forum Updated to NodeBB v4.3 + New Features

Two major problem that prevent QT webassembly used in real project.

Scheduled Pinned Locked Moved Unsolved Qt for WebAssembly
11 Posts 5 Posters 3.3k 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.
  • JoeCFDJ Offline
    JoeCFDJ Offline
    JoeCFD
    wrote on last edited by
    #2

    which Qt version is used in your project?
    you can file bugs here https://bugreports.qt.io/secure/Dashboard.jspa

    1 Reply Last reply
    0
    • JoeCFDJ Offline
      JoeCFDJ Offline
      JoeCFD
      wrote on last edited by
      #3

      @wenqing-zhong said in Two major problem that prevent QT webassembly used in real project.:

      Qt wasm

      https://stackoverflow.com/questions/63016067/build-qt-from-source-so-that-it-accepts-chinese-input

      W 1 Reply Last reply
      0
      • lorn.potterL Offline
        lorn.potterL Offline
        lorn.potter
        wrote on last edited by lorn.potter
        #4

        Hi,

        1. Use must use https for accessing threads which use javascript SharedArrayBuffer. See: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#security_requirements

        Qt Webassembly QNAM (QNetworkAccessManager) will access secure websockets (wss), just use https in the url. Also QWebSockets. If you need to use a custom certificate, you need to add it to the browser's certificates.

        1. This is fixed in 6.4 and 6.3 (or should be). See https://codereview.qt-project.org/c/qt/qtbase/+/416609
          If this doesn't fix it completely, then please open a new bug report. https://bugreports.qt.io/secure/Dashboard.jspa

        Freelance Software Engineer, Platform Maintainer QtWebAssembly, Maintainer QtSensors
        Author, Hands-On Mobile and Embedded Development with Qt 5 http://bit.ly/HandsOnMobileEmbedded

        W D 2 Replies Last reply
        1
        • JoeCFDJ JoeCFD

          @wenqing-zhong said in Two major problem that prevent QT webassembly used in real project.:

          Qt wasm

          https://stackoverflow.com/questions/63016067/build-qt-from-source-so-that-it-accepts-chinese-input

          W Offline
          W Offline
          wenqing zhong
          wrote on last edited by
          #5

          @JoeCFD
          I think that is not the problem I met, but thanks for your reply anyway. Below Mr lorn.potter's reply said my question will be solved soon.

          1 Reply Last reply
          0
          • lorn.potterL lorn.potter

            Hi,

            1. Use must use https for accessing threads which use javascript SharedArrayBuffer. See: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#security_requirements

            Qt Webassembly QNAM (QNetworkAccessManager) will access secure websockets (wss), just use https in the url. Also QWebSockets. If you need to use a custom certificate, you need to add it to the browser's certificates.

            1. This is fixed in 6.4 and 6.3 (or should be). See https://codereview.qt-project.org/c/qt/qtbase/+/416609
              If this doesn't fix it completely, then please open a new bug report. https://bugreports.qt.io/secure/Dashboard.jspa
            W Offline
            W Offline
            wenqing zhong
            wrote on last edited by
            #6

            @lorn-potter
            Thanks a lot. It's good news to hear that input bug will be solved soon.
            About the QWebsocket, I haven't use QNetworkAccessManager because I don't use http get/post operation, I will try to research more about it. I am just using QWebSocket::sendTextMessage(sendmsg) to send request to server, and use QWebSocket::textMessageReceived(QString) signal to receive the reply from server.

            1 Reply Last reply
            0
            • lorn.potterL lorn.potter

              Hi,

              1. Use must use https for accessing threads which use javascript SharedArrayBuffer. See: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer#security_requirements

              Qt Webassembly QNAM (QNetworkAccessManager) will access secure websockets (wss), just use https in the url. Also QWebSockets. If you need to use a custom certificate, you need to add it to the browser's certificates.

              1. This is fixed in 6.4 and 6.3 (or should be). See https://codereview.qt-project.org/c/qt/qtbase/+/416609
                If this doesn't fix it completely, then please open a new bug report. https://bugreports.qt.io/secure/Dashboard.jspa
              D Offline
              D Offline
              DemonCat
              wrote on last edited by
              #7

              @lorn-potter I tried 6.4.2 and 6.5.0 Beat2 and still couldn't enter Chinese

              1 Reply Last reply
              0
              • Z Offline
                Z Offline
                zhong wenqing
                wrote on last edited by
                #8

                @lorn-potter
                Hi, several monthes passed after I open an issue QTBUG-107139, but haven't found progress. Which version will this problem be solved?

                lorn.potterL 1 Reply Last reply
                0
                • Z zhong wenqing

                  @lorn-potter
                  Hi, several monthes passed after I open an issue QTBUG-107139, but haven't found progress. Which version will this problem be solved?

                  lorn.potterL Offline
                  lorn.potterL Offline
                  lorn.potter
                  wrote on last edited by
                  #9

                  @zhong-wenqing
                  The patch
                  https://codereview.qt-project.org/c/qt/qtbase/+/436295

                  is still in review. I will bump it to the reviewers again.

                  Freelance Software Engineer, Platform Maintainer QtWebAssembly, Maintainer QtSensors
                  Author, Hands-On Mobile and Embedded Development with Qt 5 http://bit.ly/HandsOnMobileEmbedded

                  Z 1 Reply Last reply
                  1
                  • lorn.potterL lorn.potter

                    @zhong-wenqing
                    The patch
                    https://codereview.qt-project.org/c/qt/qtbase/+/436295

                    is still in review. I will bump it to the reviewers again.

                    Z Offline
                    Z Offline
                    zhong wenqing
                    wrote on last edited by
                    #10

                    @lorn-potter Thanks, the qt-bug system inform me today, this patch is merged into Qt6.6. I will try it.

                    1 Reply Last reply
                    0
                    • P pgmQt referenced this topic on
                    • Z ZoltanKovacs referenced this topic on
                    • Z Offline
                      Z Offline
                      zhong wenqing
                      wrote on last edited by
                      #11

                      @lorn.potter Hi, Is this issue very difficult to resolved? or not important? the new released versions all have this problem.

                      1 Reply Last reply
                      0

                      • Login

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