ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
nerdopolis has quit [Ping timeout: 480 seconds]
guru__ has joined #wayland
nerdopolis has joined #wayland
guru_ has quit [Ping timeout: 480 seconds]
tristianc67048 has quit [Read error: Connection reset by peer]
tristianc67048 has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
cool110| has quit [Ping timeout: 480 seconds]
cool110 has joined #wayland
cool110 is now known as Guest521
garnacho has quit [Ping timeout: 480 seconds]
Guest521 has quit [Remote host closed the connection]
cool110_ has joined #wayland
cool110_ is now known as Guest522
RAOF has quit [Remote host closed the connection]
RAOF has joined #wayland
tristianc670482 has joined #wayland
tristianc67048 has quit [Ping timeout: 480 seconds]
kts has joined #wayland
tristianc670482 has quit [Read error: No route to host]
kts has quit [Ping timeout: 480 seconds]
tristianc670482 has joined #wayland
mxz__ has joined #wayland
mxz___ has joined #wayland
Company has quit [Read error: Connection reset by peer]
mxz has quit [Ping timeout: 480 seconds]
mxz___ is now known as mxz
mxz_ has quit [Ping timeout: 480 seconds]
Guest522 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest526
nerdopolis has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
glennk has joined #wayland
sima has joined #wayland
Ps1-Jack has joined #wayland
Psi-Jack has quit [Ping timeout: 480 seconds]
riteo has quit [Ping timeout: 480 seconds]
ity1 has joined #wayland
crazybyte has joined #wayland
ity has quit [Ping timeout: 480 seconds]
rv1sr has joined #wayland
crazybyte has quit [Ping timeout: 480 seconds]
JakeSays has joined #wayland
JakeSays1 has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
kts has quit [Ping timeout: 480 seconds]
<colinmarc>
yeah that's what I meant. a responsive web page uses the same CSS for mobile/desktop
<colinmarc>
I thought I read somewhere that xwayland predicates enabling passthrough on _NET_WM_STATE_FULLSCREEN, but I can't find it now. maybe I misunderstood
<colinmarc>
the reason I was asking about passthrough is that without _NET_WM_STATE_FULLSCREEN, there's clearly a blit or some sort of render happening, because the game's texture is being squished down to the correct size before it gets attached to the surface as a wayland buffer.
<colinmarc>
I get a ConfigureNotify with the correct new resolution, the wl_buffer is the correct resolution, but the game is squished/stretched and input events are incorrectly interpreted.
<karenthedorf>
There are no references to _NET_WM_STATE_FULLSCREEN anywhere in the XWayland code. (The only references in all of xserver are the X-on-win32 and x-on-x drivers)
<colinmarc>
Hm, yeah, then I'm definitely misunderstanding something :D