I was saying that the inertia scrolling should be implemented in the toolkit level, instead of emitting bogus mouse events for ‘inertia’. Which means that GTKScrolledWindow (or whatever is NSScrollView’s eqivalent is) should implement it’s functionality, not in libinput.

I considered it as fragmented b.c. the reason it was implemented this way (instead of implementing in the toolkit) was mostly because one can’t coordinate big changes in at least three big libraries (vendor drivers + libinput + Qt/GTK) to achieve something relatively small (inertia scrolling) when Apple can just decide to ‘fix everything related’ if one decides to adopt a new feature.

Not that fragmentation is a necessarily bad thing, but it’s not great in these cases.