Chromium almost works on PinePhone, two minor fixes will get it going.
Add a file at /etc/chromium/local.conf with:
unset GDK_BACKEND
Then modify /usr/share/applications/chromium.desktop and either change the --use-gl switch from desktop to egl or remove the whole switch. egl seems to work but is noisy with lots of warnings and other messages.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
On Wayland UIs one may also use Chromium's native Wayland support, as described in the ArchWiki. This would also solve XWayland oddities under Phosh. I don't understand much of the underlying stuff, but it seems that Ozone which powers this support isn't finished yet, so your solution might be better.
Edit: Nevermind, just tried it again and I have some weird input issues + in QEMU it doesn't seem to work at all.
Hey! I've just reevaluated Chromium on a clean (built last weekend) edge install with Phosh (on my PinePhone v1.2b), and it seems to work fine for me. Don't know exactly what change fixed it, but for reference, apk policy chromium yields:
[4628:4628:0406/111814.802979:ERROR:gl_implementation.cc(283)] Failed to load /usr/lib/chromium/libGLESv2.so: Error loading shared library /usr/lib/chromium/libGLESv2.so: No such file or directory
[4628:4628:0406/111814.812980:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
but it still works fine afterwards, so cautious no worries I think?
Could very well be: I tried this browser benchmark and Chromium only had a score of 1.04 while Firefox had 1.73. Funny enough, I don't notice much during normal use - scrolling is still rather smooth and page load time is fast enough (for me). But these are of course just observations, no objective benchmarks.