<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Screen size cannot rely on wl_output scale and geometry" href="https://bugs.freedesktop.org/show_bug.cgi?id=101436#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Screen size cannot rely on wl_output scale and geometry" href="https://bugs.freedesktop.org/show_bug.cgi?id=101436">bug 101436</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>Could you also clarify what "screen size" and "monitor size" mean and what they are used for via Xwayland? I kind of know what they are in X11, but I have no idea how X11 applications use them. E.g. for fullscreening, I would hope apps used WM protocols to ask what their fullscreen size should be, but I understand that's wishful thinking. So how exactly are these details used? This report sound like a continuation of the long irc discussion I had with Olivier Fourdan, where talked about how one could support HiDPI and mixed-dpi systems with Xwayland. Should we include that topic here as well? You now want to support fractional scaling behind applications' back. Was this not foreseen when the wl_output and wl_buffer scale protocol was designed? What has changed? Why is it now feasible?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>