测试了，6.5.1版本也无法输入中文。
看网上有说输入的时候在html那边生成一个输入框，生成完成后再把文本传到qt这里。

另外，虽然6.5.1的release说明说修复了中文输入问题，但是我看实际的bug还没关闭，要等待6.5.2
https://bugreports.qt.io/browse/QTBUG-107139

@pgmQt
WebAssmebly uses the browsers

When I run it and check the browsers console output, I see the message:

"Shadows are not yet supported for OpenGL ES2"

@JoeCFD said in Qt6.5.0 WebAssembly-DataVisualization does not display properly:

@Antenor https://forum.qt.io/topic/144197/full-featured-chromium-based-open-source-web-browser-with-qml-pages-support/3
Take a look at what someone did here.

It's a great idea, and it works fantastically. Since I'm going to run my desktop application (based on DataVisualization component) on the web, the best solution is that Qt Webassembly supports the DataVisualization component.
But this is also good, I'll give it a try!
Thank you for your answer!

@adazem009 The textfield inside a column layout works, inside a frame it does not.
There is nothing wrong on using anchors to set the position of the layout. One can not use anchors to set the position of the layout items. As far as i understand.

@Wangxiansheng
I still use the same approach explained in my question.
Now with qt6.6 one can select from the canvas with control+c
and paste(at least for firefox). For chrome is still giving the error of my question(this is clearly a chrome problem). The app is now compiled with qt6.6.

@mirro
I have not used WebAssembly. The following is my understanding.

You can only access the webassembly page via the JavaScript DOM. Qt QWebChannel lets you do that.

I ask again, and will not repeat further:

What are you actually trying to achieve with "How to pass parameters between webassembly for qt and htm5?"?

Maybe you do not want a full webassembly application but instead just a QWebEnginePage, I don't know.

For one, you need to use the correct emscripten version for Qt version, as detailed in:
https://doc.qt.io/qt-5/wasm.html#install-emscripten
or
https://doc.qt.io/qt-6/wasm.html#installing-emscripten

@lorn-potter

Yes I've been working with a QT Quick app. As you say, the keyboard doesn't appear normally, but I forced it to be visible. In my App.qml file I have modified the auto-generated InputPanel:

InputPanel { id: inputPanel property bool showKeyboard : active //y: showKeyboard ? parent.height - height : parent.height y: parent.height - height // ... }

Not that this fixes the keyboard. It still can't be used to enter text. But when I press a key I see an error "input method is not set" in the browser console. I'm not familiar with the input system, but maybe that's useful info for your debugging,

I will try to see if I can get the keyboard working with a QML widget in a widget app. Maybe that will be a suitable workaround.

@JonB

Hi~,How does the qmake command set the path to D:\emsdk\em++?

Here is the same code compiled with Qt 6.4.3 and emsdk 3.1.14:

http://bombmining.surge.sh/

This runs on Safari and iOS fine - and from the looks of it there have been a number of changes in the HTML, and perhaps elsewhere too between this version Qt 6.4.3 emsdk 3.1.14 and the Qt 6.5 emsdk 3.1.25 version that isn't running on iOS and Safari

Any help would be greatly appreciated, Thanks!

Any luck with the issue? I have a similar problem, when serving my Qt WASM application over HTTPS. I have not secured WebSockets in my app (as SSL seems not to work for Qt WASM) and everything works perfectly fine as long as I serve it over HTTP. When I only change it to HTTPS, even with the browser config appropriately set to handle such cases, no messages are sent from the Qt app.

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

To be safe, Emscripten 3.1.25 will work, but you could also use latest, but know that one has not been extensively tested with Qt.

@lorn-potter android

@Espoo I modified my websocket code using the sample from Qt and upgraded to 6.4.2. MQTT works fine now in WASM.