I'm a bit surprised browsers do in-scrolling events: browser performance has been under heavy optimization for years and switching to "panning mode" with no eve

I'm a bit surprised browsers do in-scrolling events: browser performance has been under heavy optimization for years and switching to "panning mode" with no events emitted while scrolling would seem like a splendid candidate for something like a "Turbo mode". Alternatively the change to disable events could've plausibly been written as a fix to usability bugs caused by in-scroll hover events. This is because I'm not sure if, since -94 or so, I've seen a single case where event handling while scrolling would have actually added to browsing usability at all. It consistently creates two kinds of problems: first laggy scrolling as elements with heavy events handlers get focused and unfocused and secondly crazy behaviour when on-hover menus will open abruptly while scrolling and the state of the page ends up messed up when the scrolling stops. It makes sense to scroll like it happens in mobile devices: the input events drive the scrolling only and the page just pans around as long as the fingers move on the screen, and the browser effectively returns to interactive mode when the scrolling stops.