<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><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">101436</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Screen size cannot rely on wl_output scale and geometry
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>XWayland
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jadahl@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>xorg-team@lists.x.org
</td>
</tr></table>
<p>
<div>
<pre>Currently, Xwayland will configure its screen and monitors given the
wl_output's it sees being advertised.
It uses the dimensions of the current mode, together with its x/y coordinate,
where each wl_output is treated as a separate monitor. The wl_output.scale
event is completely ignored.
In practice, the actual screen size and monitor sizes that Xwayland should
have, may thus be something else.
Some examples:
* A compositor may advertise a wl_output with scale 2, and have a logical pixel
coordinate space it places windows on where the content wl_output region is
also scaled by 2. Here Xwayland should treat a 1024x768 wl_output with scale 2
as 512x384 large internal monitor.
* A compositor may advertise a wl_output with scale 2 in the same way as above,
but in fact its logical representation of the output scaled with a fractional
scale, which is not advertised at all. In this case, Xwayland has no way to
know the expected screen and monitor size.
* A compositor may advertise a wl_output with scale 2, but its logical
coordinate space is always identical to the physical pixel coordinate space,
meaning Xwayland should as it does now completely ignore the wl_output scale.
To solve this, we need to introduce a protocol (Xwayland specific or not) that
communicates the logical geometry of each wl_output.</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>