00:07 wlb: wayland Issue #365 opened by Don O'Connell (donroc) FIrefox weird behavior https://gitlab.freedesktop.org/wayland/wayland/-/issues/365
08:12 MrCooper: yshui`: yeah, that sounds right; each commit is an atomic transaction
08:14 MrCooper: this gets even more interesting with synchronized sub-surfaces; committing the parent surface applies the cached sub-surface state together with the pending parent surface state as a single atomic transaction
08:15 MrCooper: (transitively with nested sub-surfaces)
10:25 pq: swick[m], do you have a typo "not" in https://gitlab.freedesktop.org/pq/color-and-hdr/-/issues/5#note_1807324 ?
10:29 MrCooper: I assume he meant "now"
12:13 swick[m]: jup
12:15 pq: swick[m], what's on your plate next for color-management or color-and-hdr? Nice spring clean-up you started. :-)
12:16 pq: any preference what I'd tackle next?
12:17 swick[m]: Not really
12:18 swick[m]: started to look into packaging stuff for fedora and get the sudden urge to do something different
12:18 pq: haha
13:18 JEEB: :D
13:18 JEEB: I think rpm style spec files weren't too bad, but it's been a real while (this was when I was poking at Tizen IVI)
13:19 JEEB: debian on the other hand was "there is no 'correct way' to build packages so just do it like you want"
13:22 wlb: wayland Merge request !297 merged \o/ (client: Do not warn about attached proxies on default queue destruction. https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/297)
13:22 wlb: wayland/main: Alexandros Frantzis * client: Do not warn about attached proxies on default queue destruction. https://gitlab.freedesktop.org/wayland/wayland/commit/b01a85dfd5e8 src/wayland-client.c tests/queue-test.c
13:26 wlb: wayland Issue #361 closed \o/ (wl_display_disconnect has misleading documentation https://gitlab.freedesktop.org/wayland/wayland/-/issues/361)
13:26 wlb: wayland/main: Simon Ser * client: fix wl_display_disconnect() documentation https://gitlab.freedesktop.org/wayland/wayland/commit/3956948fac5c src/wayland-client.c
13:26 wlb: wayland Merge request !298 merged \o/ (client: fix wl_display_disconnect() documentation https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/298)
15:10 pq: swick[m], let me know if you start on anything for the protocol or color-and-hdr, so I don't pick the same.
15:10 pq: swick[m], I'm thinking of maybe going through the open threads in !14, or tackling well_known.rst.
15:10 swick[m]: will do
15:10 swick[m]: both sound like good ideas
15:11 pq: cool
16:18 wlb: wayland Issue #365 closed \o/ (FIrefox weird behavior https://gitlab.freedesktop.org/wayland/wayland/-/issues/365)
19:00 kchibisov: Is it correct that wp_viewporter::set_destination is double buffered? It's not exactly clear that it is.
19:01 kchibisov: I'd assume yes, because it mentions "Crop and scale" inside the wp_viewport description.
19:02 vyivel: kchibisov: yes, viewport properties are double-buffered
19:03 kchibisov: I'm just used to different wording wrt it, because it's stated explictly that 'The XXX is double buffered'.
20:39 wlb: weston Merge request !1184 opened by Derek Foreman (derekf) Rework 2D coordinate handling part 5 https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1184 [Input], [Core compositor], [libweston API]
20:49 wlb: weston Merge request !1185 opened by Derek Foreman (derekf) compositor: Rename position.set to position.changed https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1185 [Core compositor]
22:32 wlb: wayland Issue #366 opened by i509VCB (i509VCB) Question around destruction of surfaces with pointer and keyboard focus https://gitlab.freedesktop.org/wayland/wayland/-/issues/366