Bug 81225
| Summary: | Make GestureScrollBegin an optional event in a scroll-fling sequence | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Robert Kroeger <rjkroege> |
| Component: | UI Events | Assignee: | Robert Kroeger <rjkroege> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | davemoore, jamesr, rjkroege |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 81409 | ||
| Bug Blocks: | |||
Robert Kroeger
The chromium embedder needs to be flexible in its inclusion of GestureScrollBegin in a gesture scroll sequence.
in particular:
ScrollBegin ScrollUpdate ScrollUpdate ScrollUpdate ScrollEnd
should be equivalent to
ScrollUpdate ScrollUpdate ScrollUpdate ScrollEnd
with regards to initiating a scroll.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Robert Kroeger
NB: I will presume that GestureScrollUpdates will be fully populated with valid positions when writing the necessary tests.
James Robinson
I think this is just bogus. Why would we need to do that? If the GestureScrollBegin has no purpose then we shouldn't be getting one.
Robert Kroeger
Per discussion, the bug is indeed bogus.