ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
kode544 has joined #wayland
MrCooper__ has joined #wayland
MrCooper_ has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
kode54 has quit [Ping timeout: 480 seconds]
karenw has quit [Ping timeout: 480 seconds]
Company has quit [Ping timeout: 480 seconds]
d42 has quit [Read error: Connection reset by peer]
d42 has joined #wayland
Company has joined #wayland
FreeFull has quit []
Moprius has quit [Quit: bye]
Brainium has quit [Quit: Konversation terminated!]
abeltramo5895238271976 has quit [Quit: Ping timeout (120 seconds)]
alarumbe has quit [Remote host closed the connection]
alarumbe has joined #wayland
abeltramo5895238271976 has joined #wayland
Company has quit [Ping timeout: 480 seconds]
Company has joined #wayland
nerdopolis_ has joined #wayland
nerdopolis is now known as Guest12723
nerdopolis_ is now known as nerdopolis
Guest12723 has quit [Ping timeout: 480 seconds]
MrCooper_ has joined #wayland
MrCooper__ has quit [Ping timeout: 480 seconds]
garnacho has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
Company has quit [Ping timeout: 480 seconds]
aswar002_ has joined #wayland
aswar002 has quit [Ping timeout: 480 seconds]
feaneron has quit [Ping timeout: 480 seconds]
shankaru1 has joined #wayland
shankaru has quit [Ping timeout: 480 seconds]
hugeblank has quit [Quit: WeeChat 4.5.2]
aelius has quit [Remote host closed the connection]
<nickdiego[m]>
jadahl emersion I wonder what would be the best way to (tentatively) move xdp-pip forward at this point? maybe prototyping something? or do you think there are still major unresolved design concerns to be addressed?
fmuellner has joined #wayland
<zzag>
nickdiego[m]: there is no consensus over whether the clients are allowed to present their own controls in pip
<zzag>
with my KDE hat, we would prefer if the clients are responsible for that and instead have the compositor enforce other constraints, like size, etc
<nickdiego[m]>
Right, assuming we'd like it to be w3c-compatible, that'd be probably a requirement I think
karenw has joined #wayland
tzimmermann has quit [Quit: Leaving]
<nickdiego[m]>
<nickdiego[m]> "Right, assuming we'd like it..." <- I mean, the ability to control what gets actually rendered to the pip surface
<swick[m]>
nickdiego: do you know how the w3c spec is supposed to be implemented on iOS and Android?
mclasen has quit [Ping timeout: 480 seconds]
coldfeet has quit [Quit: Lost terminal]
mohit815822635306 has quit [Quit: mohit815822635306]
mohit815822635306 has joined #wayland
melnary has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
karenw has joined #wayland
___nick___ has quit [Remote host closed the connection]
mvlad has quit [Remote host closed the connection]
melnary has joined #wayland
<nickdiego[m]>
<swick[m]> "nickdiego: do you know how the w..." <- tbh I don't know. I'd guess some parts (eg: arbitrary content rendering) will be left unimplemented where the platform doesn't support it
<nickdiego[m]>
seems worth filing an issue in the spec repo to discuss that with the editors
flom84 has joined #wayland
flom84 has quit []
<jadahl>
nickdiego[m]: mind doing that (file issues about platform implementability)?
sqwishy4 has joined #wayland
sima has quit [Ping timeout: 480 seconds]
sqwishy has quit [Ping timeout: 480 seconds]
sqwishy4 is now known as sqwishy
<nickdiego[m]>
<jadahl> "nickdiego: mind doing that (file..." <- I can start that discussion yes. Though regarding it, what would be the position of wayland as a platform? reservations about security?
Net147 has joined #wayland
Net147_ has quit [Read error: Connection reset by peer]
mclasen has joined #wayland
<nickdiego[m]>
Also, that's a draft spec proposal. Alternatively, we could start with a protocol that supports the current w3c spec (ie: no arbitrary content in pip windows), and discuss it for a potential v2, if applicable. wdyt?
<nickdiego[m]>
It's currently at [working draft](https://www.w3.org/standards/types/#CG-DRAFT) level, which is much more advanced that the one for "Document Picture-in-picture" (linked above)
karenw has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
<nickdiego[m]>
* API: https://www.w3.org/TR/picture-in-picture/ It's currently at working draft level, which is much more advanced than the one for "Document Picture-in-picture" (linked above)
<vyivel>
nickdiego[m]: please refrain from editing your messages, it doesn't look that well on irc side
<nickdiego[m]>
qck and sorry for the noise
<nickdiego[m]>
ack*
<emersion>
nickdiego[m]: yeah zzag's point is the main blocker i think. i agree with zzag here and would prefer the client to provide the controls
yrlf has quit [Quit: Ping timeout (120 seconds)]
yrlf has joined #wayland
akimoto has quit [Remote host closed the connection]
<nickdiego[m]>
@_oftc_emersion:matrix.org thanks for the feedback! I've chatted a bit with zzag, and we agreed on putting up a kwin+chromium prototype, iiuc following the client-controlled approach. in the meantime I'll start a thread with "document pip" spec editors to discuss implementability as suggested by jadhal