зеркало из https://github.com/mozilla/gecko-dev.git
023bd8d65c
This is what Safari does, i.e. once after a swipe gesture has started to a direction where there is no navigation history, then even if the swipe gesture switched to the opposite direction where navigation can happen, swipe navigation will never happen. Chrome looks like they are trying to do swipe navigation in such cases, but it looks like they sometimes fail it, the swipe navigation indicator (an arrow image) doesn't show up sometime when the swipe navigation goes to the opposite direction. This change fixes stuck-in-overscroll situations where user swipes horizontally to a direction where navigation is impossible during overscrolling, but doesn't fix situations where navigation is possible but the user cancels the navigation. To fix the later situations we need a different fix apart from this change. The mochitest in this change doesn't test the stuck-in-overscroll situations at all because we need to write a browser mochitest since swipe gesture is implemented as a browser feature but unfortunately SpecialPowers.snapshotWindow doesn't capture overscrolled gutter regions for some reasons, so instead the test checks whether the swipe gesture module keeps capturing wheel events in the situations where navigation is impossible. Differential Revision: https://phabricator.services.mozilla.com/D113636 |
||
|---|---|---|
| .. | ||
| browser.ini | ||
| browser_test_clipboardcache.js | ||
| browser_test_swipe_gesture.js | ||