<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c3">Comment # 3</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 <span class="vcard"><a class="email" href="mailto:fourdan@xfce.org" title="Olivier Fourdan <fourdan@xfce.org>"> <span class="fn">Olivier Fourdan</span></a>
</span></b>
<pre>(In reply to Jonas Ådahl from <a href="show_bug.cgi?id=101436#c2">comment #2</a>)
<span class="quote">> (In reply to Pekka Paalanen from <a href="show_bug.cgi?id=101436#c1">comment #1</a>)
> [...]
> >
> > 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?
> >
>
> How maximize and fullscreen works I'm not very familiar with.</span >
For maximized state and fullscreen, x11 apps use the relevant EWMH protocol:
* _NET_WM_STATE for maximized and "normal" fullscreen [1]
* _NET_WM_FULLSCREEN_MONITORS for fulscreen across different monitors [2]
The later uses Xinerama monitor indices to list the monitors (!)
[1]
<a href="https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472615568">https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472615568</a>
[2]
<a href="https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472531472">https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472531472</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>