X11 had horrible tearing on external rotated screens - Wayland fixed that.
Colour temperature changing works.
Screensharing works just fine on Chrome and Firefox. I use it every day.
Screen recording works with Gnome's built in recorder.
I'm sure there are a few esoteric bits which don't work - but I've had nothing but success with it.
okay, but what if I don't like gnome ? e.g. I had to record a screencap of a bug of a software (that, uh, occurs only under wayland) so I went under weston and, well apparently there is also a screen capture tool but it is incompatible. On X11 I use simplescreenrecorder no matter the desktop (I mostly use i3wm or KDE Plasma depending on the circumstances).
Also what's the way to set a different keymap, that would work for any wayland compositor ? `setxkbmap` used to work but doesn't anymore and this is fairly frustrating and I really really don't want to have to learn one command per compositor.
Moving windows (or even the mouse cursor) also feels absolutely sluggish on wayland, like the frame rate is halved.
X11 / i3 : https://streamable.com/fo8ixw
weston-eglstream : https://streamable.com/wmp6vy
Also switching in/out from a wayland tty apparently gets it stuck here.
etc etc... it's just painful from start to end
Under X11, the screen capture and recording doesn't work when one of my screen is scaled and rotated. The capture will turn entirely black, even when capturing on my other screens. If I want to capture something, I need to unplug that monitor (or change my xrandr settings to put it back to horizontal).
Works just fine under Wayland with Sway.
Improvements in X11 break software all the time too. It's not a wayland thing.
So it took a while for screen capture to work on Wayland. I agree that it was questionable for distros like Fedora to move to Wayland before such a critical feature was working, but now it works.
Because Wayland is a protocol with no canonical implementation, it is going to take a bit of time for all compositors to implement the new standard for screen capture. But gnome has implemented it, so has wlroots, and I assume KDE has or soon will. Weston is a toy compositor, not intended for serious use, so it's not surprising if it lags behind.
Firefox is quite buggy on Wayland, you need to set up some environment flags before launching it, and there's a trove of bugs still open for it.
https://bugzilla.mozilla.org/show_bug.cgi?id=635134
> I'm sure there are a few esoteric bits which don't work
Like cut and paste between different kind of applications, which is an horrible user experience tbh.
You will probably also want to force enable webrender (gfx.webrender.all = true in about:config), which still isn't on by default apparently.
I've used this for more than a year on Sway. Recently I had some issues with addon dialogues , but mostly it's been running just fine and with best in class performance, very noticeably faster than Chrome.
With the environment flag, it works pretty well.
On Gnome, plugins can cause issues. hidetopbar, for example, had an issue with Firefox when the screens are stacked vertically.
The main thing that annoys me with firefox is drop-down menus don't respond to clicks properly so I'm forced to use the arrow keys.
Is it? I moved to Sway (a Wayland WM) a few months ago, and run FF exclusively. Hell, I even run Firefox ESR (as provided by Debian), and I've noticed precisely one bug, and it's tiny: the main FF hamburger menu has a vertical scrollbar even if it's got plenty of vertical space left on the screen. Whatever, I use that menu once in a blue moon. Everything else is perfect!
What are you experiencing?
> you need to set up some environment flags before launching it
A single flag! Come on, this is hardly a problem.
> and there's a trove of bugs still open for it.
There's a trove of bugs open for FF in general ;-)
> Like cut and paste between different kind of applications, which is an horrible user experience tbh.
What do you mean? It works fine for me. From FF to other Wayland windows, from other Wayland windows to FF, and to and from Xwayland windows. The only copy/paste behavioral difference I've noticed on Wayland is that I lose the copied data if I close the source program. So when copying from FF, I can't close FF (as a whole, not talking about the window in question) before I've pasted. I can't see that this is an actual problem.
This is because sway by default does not provide a "clipboard manager" component. It has been the case for a long time that the clipboard is only actually populated when you paste, copying merely stores a reference. This is so you can copy/paste multi gigabyte files without running out of memory. A clipboard manager component solves this issue by intelligently saving your clipboard as applications come and go.
Honest question: Is this something that people are missing in Wayland?
I'm using Ubuntu 20.04 on an XPS13 and can finally have different scaling factors between the internal HiDPI screen and external normal DPI screen without awful issues.
Some monitors also have unusual dpi where they are HiPDI but don't suit 2x UI scaling. A very popular LG USB-C 4K monitor is in that camp.
√(3840²+2160²)÷275 ≅ 16
For the external monitor to have the same dpi as the laptop, it would need to be a 16K resolution monitor.
I _am_ disappointed in that fractional scaling is not first-class :(
I have screens with different DPI attached to my linux machine running X/nvidia. A bit of futzing around with xrandr had it sorted.
Did you manage to setup more than 1 monitor to run on various (an sometimes very different) dpi settings?
On the other hand, the reason I switched to Wayland was that I wasn't able to get multiple monitors with different pixel densities working in Xorg. That works fine in Wayland, and since one of my monitors was unusable without being able to choose different pixel densities for each monitor, Wayland it is.
If it matters, I'm using Pop OS on a System76 Thelio.
I have set up fractional scaling of different fractions on all three of my screens. No issues on Wayland.
When electron 12 is released and slack will be build using it, it will be possible to use slack as a native wayland application and then screensharing should work.
That never worked under X11 either so not a problem with wayland, just it would be nice to find a solution.
And so it on X11.