This comment indicates to set `MOZ_ENABLE_WAYLAND=1` in your `~/.profile` to force Firefox to use Wayland.
With this environment variable on, the issue does not appear anymore.
Also worth noting: a comment (commenter @aeno still on [my askubuntu.com question](https://askubuntu.com/a/1455694)) mentions that he/she experiences the issue on ArchLinux (with Wayland).
Someone pointed me to a comment on bugzilla:
* [someone's answer on askubuntu.com](https:/ /askubuntu. com/a/1455694/ 18501) /bugzilla. mozilla. org/show_ bug.cgi? id=1774531# c25)
* [the comment to issue 1774531 on bugzilla](https:/
This comment indicates to set `MOZ_ENABLE_ WAYLAND= 1` in your `~/.profile` to force Firefox to use Wayland.
With this environment variable on, the issue does not appear anymore.
Also worth noting: a comment (commenter @aeno still on [my askubuntu.com question](https:/ /askubuntu. com/a/1455694)) mentions that he/she experiences the issue on ArchLinux (with Wayland).
It looks like this issue is not Ubuntu specific.