ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
MrCooper_ has joined #wayland
MrCooper has quit [Read error: Connection reset by peer]
garnacho has quit [Remote host closed the connection]
garnacho has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
yshui_ has joined #wayland
yshui has quit [Ping timeout: 480 seconds]
glennk has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Quit: No Ping reply in 180 seconds.]
nerdopolis has joined #wayland
Consolatis has quit [Quit: ZNC 1.8.2+deb2+deb11u1 - https://znc.in]
Consolatis has joined #wayland
lsd|2|2 has quit [Ping timeout: 480 seconds]
Calandracas_ has quit [Ping timeout: 480 seconds]
nerdopolis_ has joined #wayland
nerdopolis is now known as Guest5859
nerdopolis_ is now known as nerdopolis
Guest5859 has quit [Read error: Connection reset by peer]
Brainium has quit [Quit: Konversation terminated!]
Moprius has quit [Quit: bye]
Moprius has joined #wayland
Moprius has quit [Remote host closed the connection]
nerdopolis has quit [Ping timeout: 480 seconds]
eluks has quit [Remote host closed the connection]
eluks has joined #wayland
crazybyte has quit [Quit: Bye]
crazybyte has joined #wayland
bindu_ has joined #wayland
bindu has quit [Ping timeout: 480 seconds]
tzimmermann has joined #wayland
shoragan has joined #wayland
iomari891 has joined #wayland
leon-anavi has joined #wayland
mvlad has joined #wayland
sima has joined #wayland
<any1>
outfoxxed[m]: A new buffer can be considered fully damaged, yes.
<any1>
Those long matrix links get wrapped in my IRC client and other "UI elements" interfere with selection.
<outfoxxed[m]>
<any1> "outfoxxed: A new buffer can be..." <- is the compositor supposed to track that its a new buffer or am I though
<outfoxxed[m]>
I'm assuming the client should
chiku has quit [Ping timeout: 480 seconds]
rgallaispou has joined #wayland
Sid127 has joined #wayland
<pq>
outfoxxed[m], a Wayland client should never assume that a compositor adds full wl_surface damage when it attaches and commits a wl_buffer that leads to a different wl_surface size.
<outfoxxed[m]>
This isn't wl_surface damage, this is ext_image_copy_capture_frame damage, but I assume its the same
<pq>
Making sure that wl_surface damage is sufficient is the client's responsibility.