[00:16] <RAOF> Maybe they're getting the patch? It's not particularly invasive.
[00:17] <RAOF> Alternatively: maybe they're not supporting EGL on mirclient? The only components which need mirclient are the various lomiri infrastructures, and they're going to be reasonably happy with a software renderer.
[02:49] -GitHub[m]:#mir-server- **[MirServer/mir]** RAOF opened [pull request #2747](https://github.com/MirServer/mir/pull/2747): cmake: Fix ptest target... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/0be3de2576a23b8f1511d76a04d43087e7ea99ec>)
[03:00] -GitHub[m]:#mir-server- **[MirServer/mir]** RAOF edited [pull request #2744](https://github.com/MirServer/mir/pull/2744): Add core mmap-backed SHM handling
[04:13] -GitHub[m]:#mir-server- **[MirServer/mir]** RAOF assigned  to [pull request #2747](https://github.com/MirServer/mir/pull/2747): cmake: Fix ptest target
[08:13] <Saviq> Good weekend o/
[08:19] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [issue #2748](https://github.com/MirServer/mir/issues/2748): wlcs.Anchor/LayerSurfaceLayoutTest.is_positioned_to_accommodate_other_surfaces_exclusive_zone unstable... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/a637038f101c14ce3b0a04ba771cc0d43c88524e>)
[08:20] <Saviq> Good morn'
[09:06] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq requested a review from AlanGriffiths for [pull request #2744](https://github.com/MirServer/mir/pull/2744): Add core mmap-backed SHM handling
[09:49] <alan_g[m]> Saviq, if you want to fixup #2747 we can land it and the follow-on
[09:49] <Saviq> Sure, I can
[09:50] <alan_g[m]> I'll poke at #2748
[15:19] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2749](https://github.com/MirServer/mir/pull/2749): Fix race... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/2c6954f1014175e57bacba99d79fccd49a5cccdb>)
[15:33] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq requested a review from wmww for [pull request #2749](https://github.com/MirServer/mir/pull/2749): Fix race
[15:49] -GitHub[m]:#mir-server- **[MirServer/wlcs]** AlanGriffiths drafted [pull request #257](https://github.com/MirServer/wlcs/pull/257): test
[15:50] -GitHub[m]:#mir-server- **[MirServer/wlcs]** AlanGriffiths edited [pull request #257](https://github.com/MirServer/wlcs/pull/257): test
[17:09] <Saviq> Good night o/
[17:12] <grayson-g[m]> Does anyone know where touch scrolling is implemented? I'm working on the touch drag code right now and it prioritizes scrolling over starting a drag event.
[17:13] <alan_g[m]> In the client toolkit?
[17:18] <grayson-g[m]> alan_g[m]: Thanks! Poking around right now.
[20:46] <sophie-w> There's no guarantee that clients implement touch drag and drop
 "There's no guarantee that..." <- Huh, sure enough I can't drag on Weston with touch in either Firefox or Chrome. Reading over the specification for `wl_data_device`, it *never mentions* touch. I wonder if any clients have it implemented 🤔
[21:06] <grayson-g[m]> > <@wmww:matrix.org> There's no guarantee that clients implement touch drag and drop
[21:06] <grayson-g[m]>  * Huh, sure enough I can't drag on Weston with touch in either Firefox or Chrome. Reading over the specification for `wl_data_device`, it _never mentions_ touch with regard to drag-and-drop. I wonder if any clients have it implemented 🤔
[21:07] <grayson-g[m]> grayson-g[m]: In fact, `wl_data_device::enter` explicitly describes its x and y arguments as "the position of the pointer." huh
[21:24] <grayson-g[m]> I feel like this means I should remove all touch-related logic from drag-and-drop. Any differing opinions?
 "I feel like this means I..." <- Oh, wow. GTK's touch support is surprisingly poor.
[22:18] <RAOF> RAOF: That's a +1 on removing touch-related logic from drag&drop.
[23:29] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2743](https://github.com/MirServer/mir/pull/2743): Drop server/graphics/gl_extensions_base.cpp; it's dead code