fb8832de9c
Since we cannot rely on the clients specifying a suitable CSP that will not forbid execution of js injections, we have to refrain from using any explicit <script> elements. To keep the promise system working, a thunk pool was introduced which keeps track of a limited pool of promise callback exports. In case the resources are busy, pending calls are enqueued. This works since the JS Promise.then/catch/finally always fire, even on ready/failed promises. As the situation of full thunk pool allocation is unlikely to happen en masse IRL, the solution should not adversely affect the performance. Heavy unit tests were created to confirm the solution works as expected. Task-number: QTBUG-99611 Change-Id: I0e6982d4ee76a4263b59e72b004b3ff2f167e4df Reviewed-by: Morten Johan Sørvig <morten.sorvig@qt.io> |
||
|---|---|---|
| .. | ||
| a11y | ||
| clipboard | ||
| cursors | ||
| eventloop | ||
| localfiles | ||
| qstdweb | ||
| qtwasmtestlib | ||
| rasterwindow | ||
| CMakeLists.txt | ||
| README.md | ||
Manual tests and examples for Qt on WebAssembly
These examples demonstrates various technical aspects of the Qt for WebAssambly platform port, and can be used as a reference when writing application code.
Content
cursors Cursor handling
eventloop Event loops, application startup, dialog exec()
localfiles Local file download and upload
rasterwindow Basic GUI app, event handling
qtwasmtestlib native auto test framework