06:49wlb: weston Merge request !1713 merged \o/ (clients/simple-egl: trivial cleanup fixes https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1713)
06:49wlb: weston/main: Erico Nunes * clients/simple-egl: remove duplicated shader program link https://gitlab.freedesktop.org/wayland/weston/commit/4fa4665d7a92 clients/simple-egl.c
06:49wlb: weston/main: Erico Nunes * clients/simple-egl: destroy tearing_manager on exit https://gitlab.freedesktop.org/wayland/weston/commit/ae47d27f063a clients/simple-egl.c
07:06wlb: weston Merge request !1714 opened by Marius Vlad (mvlad) gitlab-ci.yml: Limit gcov and perfetto to just x86 build https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1714 [CI]
13:04wlb: weston Merge request !1715 opened by Loïc Molinari (molinari) compositor: Fix up damage area of scaled surfaces https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1715 [Core compositor]
14:06wlb: weston/main: Marius Vlad * backend-drm: Fix count page flips on invalid outputs https://gitlab.freedesktop.org/wayland/weston/commit/9aa910c4d4b7 libweston/backend-drm/kms.c
14:06wlb: weston Merge request !1706 merged \o/ (backend-drm: Fix count page flips on invalid outputs https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1706)
14:10jadahl: zamundaaa[m]: a week passed (https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/238). someone complained but not with anything new. time to merge anyway?
14:12zamundaaa[m]: Yeah, I don't think we'll find a better name anymore
14:14emersion: agreed
15:06wlb: wayland-protocols/main: Xaver Hugl * meson: sort protocols alphabetically https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/7636151e4a5a meson.build
15:06wlb: wayland-protocols/main: Xaver Hugl * staging: add toplevel tag protocol https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/723270ad4a32 staging/xdg-toplevel-tag/README staging/xdg-toplevel-tag/xdg-toplevel-tag-v1.xml meson.build
15:06wlb: wayland-protocols Merge request !238 merged \o/ (staging: add toplevel tag protocol https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/238)
15:13nickdiego[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?
15:15zzag: nickdiego[m]: there is no consensus over whether the clients are allowed to present their own controls in pip
15:16zzag: 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
15:19nickdiego[m]: Right, assuming we'd like it to be w3c-compatible, that'd be probably a requirement I think
16:02nickdiego[m]: <nickdiego[m]> "Right, assuming we'd like it..." <- I mean, the ability to control what gets actually rendered to the pip surface
18:25wlb: weston/main: Michael Olbrich * backend-drm: make sure outputs are enabled during plane assignment https://gitlab.freedesktop.org/wayland/weston/commit/83053f0ce438 libweston/backend-drm/ drm.c state-propose.c
18:25wlb: weston Merge request !1685 merged \o/ (backend-drm: make sure outputs are enabled during plane assignment https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1685)
18:50wlb: weston Merge request !1716 opened by Derek Foreman (derekf) compositor: Fix a potential crash at shutdown https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1716 [Core compositor]
19:01swick[m]: nickdiego: do you know how the w3c spec is supposed to be implemented on iOS and Android?
20:15nickdiego[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
20:16nickdiego[m]: seems worth filing an issue in the spec repo to discuss that with the editors
20:20jadahl: nickdiego[m]: mind doing that (file issues about platform implementability)?
20:34nickdiego[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?
20:37nickdiego[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?
20:37nickdiego[m]: * that's a [draft spec, * spec proposal](https://wicg., * .github.io/document-picture-in-picture/). Alternatively,
21:15jadahl: nickdiego[m]: I guess the position of Wayland is simply undecided
21:15jadahl: the concerns are primarily the same as w3c I guess, i.e. hinder abuse and misuse
21:17nickdiego[m]: right thanks
21:18nickdiego[m]: so, IIUC, this is the currently established video-only version of the picture-in-picture web API: https://www.w3.org/TR/picture-in-picture/
21:24nickdiego[m]: * so, IIUC, this is the currently established video-only version of the picture-in-picture web API: https://www.w3.org/TR/picture-in-picture/
21:24nickdiego[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)
22:23nickdiego[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)
22:26vyivel: nickdiego[m]: please refrain from editing your messages, it doesn't look that well on irc side
22:27nickdiego[m]: qck and sorry for the noise
22:27nickdiego[m]: ack*
22:36emersion: 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
23:15nickdiego[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