The bug depends on a few factors that aren't really packaging-specific. A) the default socket buffer size B) the polling rate of your mouse C) whether there's a

The bug depends on a few factors that aren't really packaging-specific. A) the default socket buffer size B) the polling rate of your mouse C) whether there's anything on your system or in your firefox profile that can cause enough lag that the buffer overflows D) whether your compositor has any workarounds for that protocol limitation Well, I suppose a packager could have disabled wayland in firefox...