Firefox running through XWayland is very choppy on my device. So I made this version that uses Wayland for rendering.
Source:
https://gitlab.com/asrpo/firefoxwayland
Experimental! Use at your own risk!
Let me know of any not-already-known issue.
- On-screen keyboard sometimes needs a long press followed a short press to reappear.
- Flickering on initial page load
Any plans to push it upstream when the kinks are ironed out?
Upstream to where? Someone working on UT said they’re working on Mir/qmir which could potentially make the patching unnecessary. But seems like that’s not working yet.
To Mozilla.
That’s an interesting suggestion. If they want it, I’m more than happy to contribute. I just don’t know what they think of keeping a flag for this particular quirk of this particular Wayland-compatible server.
Maybe in Firefox 138 and earlier it’d have been easier because very few lines change. I don’t have a patch for the latest Firefox though and would only work on it if I know Moizlla wants it.