I think this project should have proper end-to-end tests to be more stable and maintainable in the long term. That is, automate the checking that the wayland/windows/etc ports actually work properly.
Perhaps I could help by writing the first end-to-end webassembly test. I maintain chromedp, which can be used to drive Chrome via pure Go, so I think that would be a good option for the use case. The test would simply be skipped if Chrome isn't installed.
If that seems like a good idea, I can send a small patch. Ideas are welcome on what kind of features we could test as a start; I was thinking simply an app that changes background color when clicked anywhere. That would be pretty trivial to test via chromedp, issuing a click at a fixed coordinate, and getting the color at the same coordinate.
Yes, please! I've been wanting to set up Sourcehut builders for a while now; this issue is a good reason to do so.
I think this is resolved, with basic coverage for x11, wayland, and JS.