Comment 30 for bug 728643
Revision history for this message
| Chase Douglas (chasedouglas) wrote Re: Kinetic scrolling implementation continues to send scroll event after physical action has stopped | #30 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Due to the way scroll events are handled in X today, there's no way around this. The scroll events are generated in the X input module, which has no idea of what is really going on on the desktop. One could say that your application should see the closure of a tab and then ignore all scroll events until scrolling stops, but scroll events are handled as button presses so the X client doesn't know when scrolling has stopped. This issue can also be found in OS X where you can do similar things.
The goal is to replace X input module scroll events with utouch gesture events. These events can know about the window hierarchy so they terminate when a window is closed. The gestures also have a start and a stop, allowing the utouch client to stop handling a scroll gesture when the tab has closed until the gesture ends.
Because there's no real resolution to this issue in the current toolkits/X, I'm closing this as Won't Fix.