Comment 35 for bug 728643

One can also trigger kinetic scrolling, move the pointer and have the mousewheel clicks land in an undesired location, e.g., by scrolling in chromium and immediately moving the pointer to the tab area.

Surely the synaptics driver is in a position to be able to stop kinetic scrolling when the pointer is moved (at all, or beyond a threshold). I can't think of a situation where the current behaviour is desirable. Similarly (although I believe this would involve two separate drivers talking to each other, so I'm unsure about how easy this would be), the synaptics driver should stop sending these delayed events if the status of any keyboard modifier changes, which would address the bug reported here.