Why? What? Why? The system exactly knows the DPI of all attached displays, why does it still need explicit configuration in 2020 to support HiDPI?!
Sway already detects hidpi displays based on a heuristic from EDID info and chooses an appropriate scale factor.
https://github.com/swaywm/sway/issues/1800
8, now 9, comments in a subthread because no one could bother to validate assumptions or do a Google search.
We've inherited a lot of baggage and odd conventions, some of which were wrong to begin with. I don't think we should be carrying on with it if we can do better. Having these scaling factors directly correspond to physical reality would be a start.
I just start new xorg session for screenshare, which, frankly, sucks.
EDIT. I misread Slack for Zoom.
Slack is still a pain point for me as well, but mainly because Slack continues to demand that I install the desktop app for calls/screen sharing.
Zoom's desktop app also doesn't work, but I can use zoom-redirector and have the calls immediately open in my browser (you can get the same thing without the extension, but it requires you pretend that you can't install their desktop app and several button presses for every meeting).
My guess is that we're about 12 months away from having it work by default in most places.
Clipboard works perfectly splendid, screen-sharing works (not as perfectly splendid as clipboard does), input works, chromium/electron is getting support for native wayland. Qt and GTK Wayland support's quite good.
I have had no problems whatsoever and I invite you to try it. I have no hard-proof evidence or numbers to support my opinion, just try it.