From Elias Naur to ~eliasnaur/gio
Hi Dominik, Thank you very much for thinking about these issues. On Sun, 3 Sept 2023 at 08:26, Dominik Honnef <dominik@honnef.co> wrote: > > Using nested scrollable areas, as implemented in Gio (and many other > frameworks), leads to the following two bad user experiences when using > the scroll wheel: > > 1. The user starts scrolling the outer area. The inner scrollable area > happens to scroll into view and is positioned under the cursor. The > inner area now hijacks the scrolling action, and the user can no > longer scroll the outer area without moving their cursor to an area
From Elias Naur to ~eliasnaur/gio-patches
Merged, thank you. Elias
From Elias Naur to ~eliasnaur/gio-patches
Merged, thank you. Elias
From Elias Naur to ~eliasnaur/gio-patches
Merged, thanks. Elias
From Elias Naur to ~eliasnaur/gio-patches
Merged, thanks. Elias
From Elias Naur to ~eliasnaur/gio-patches
Merged, thanks. Elias
From Elias Naur to ~eliasnaur/gio-patches
Merged, thanks. Elias
From Elias Naur to ~eliasnaur/gio-patches
Thanks, merged. Elias
From Elias Naur to ~eliasnaur/gio-patches
On Mon, 21 Aug 2023 at 11:00, Chris Waldon <christopher.waldon.dev@gmail.com> wrote: > > Do you think the same change should be made for SemanticAt? I wasn't > sure whether that case really only wanted to consider the topmost area > or not. Probably yes? I'm so far away from semantic ops that I don't remember whether there was a particular reason to do otherwise. Elias
From Elias Naur to ~eliasnaur/gio-patches
Thanks a lot. Merged. Elias