zlacker

>"You might want to check out that it's using hardware acceleration properly, and that's it's configured correctly to use wayland if you're on wayland."

Maybe it should be browser's task to do it. As a user I just do not want to waste my time on things like that unless they're vital. In this case I'll just use different browser.

>>FpUser+(OP)
> Maybe it should be browser's task to do it.

Unfortunately you don't really get that luxury if you use Linux.

>>FpUser+(OP)
Running Linux on a desktop pretty much guarantees that you have an endless parade of small problems to fix.

I really wish this weren't true, but the user experience has barely improved in the past 15-20 years. The specific problems may be different, but it's still the same struggle.

>>FpUser+(OP)
Takes time to migrate to a completely new display manager :) For now it's opt-in, in the future it'll obviously be default if you're on Wayland.

If you don't like bleeding edge, warts or sometimes unpolished experiences, might be better to go with Windows or macOS, no one would blame you.

>>capabl+Bh
I use both Windows and Linux. Linux runs on server and workstation class hardware dedicated for deployment mostly so the last thing I care about is what / how browsers run on those.

>>FpUser+(OP)
That's completely fair. The reason that everyone is half-in on Wayland is likely because it's not yet default on Ubuntu. That, and Gnome window decorations.

>>FpUser+fw
So you don't run browsers on Linux, I don't see what you have a problem with then? The particular issue you're complaining about doesn't seem to affect you at all.

>>capabl+Ft2
Where did you see me complaining about the issue? I just stated my opinion that it should be in general task of the software to figure out the environment it is running under and adjust accordingly.