First frame not perfect on HiDPI screen
When displaying a surface on a HiDPI screen (e.g. wl_output.scale = 2), the first frame rendered by clients is not perfect: it's drawn with scale = 1. This happens because compositors send wl_surface.enter after a surface is mapped.
Right after pushing the first frame, clients will receive wl_surface.enter and will be able to render at the correct scale.
I'm wondering whether it would be legal for a compositor to send wl_surface.enter to an unmapped surface, in the case where the compositor knows on which output the surface will show up when mapped.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information