Bug 1916010 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Actually, I don't think that would work - we'll want to compare the current scroll position to the scroll position at the start of the gesture. So we'll need to know what the scroll position was at the start of the gesture. If the position has changed between two gestures (e.g. due to programmatic scrolling), how would we get an accurate initial value, if we weren't notified of those changes?
Actually, I don't think that would work - for determining how much of the toolbar to reveal, Fenix will want to compare the current scroll position to the scroll position at the start of the gesture. So Fenix needs to know what the scroll position was at the beginning of the gesture. If the position has changed between two gestures (e.g. due to programmatic scrolling), how would we get an accurate initial value, if we weren't notified of those between-gesture changes?
Actually, I don't think that would work - for determining how much of the toolbar to reveal, Fenix will want to compare the current scroll position to what the scroll position was at the start of the gesture. So Fenix needs to know what the scroll position was at the beginning of the gesture. If the position has changed between two gestures (e.g. due to programmatic scrolling), how would we get an accurate initial value, if we weren't notified of those between-gesture changes?
Actually, I don't think that would work - for determining how much of the toolbar to reveal, Fenix will want to compare the current scroll position to what the scroll position was at the beginning of the gesture. So Fenix needs to know what the scroll position was at the beginning of the gesture. If the scroll position has changed between two gestures (e.g. due to programmatic scrolling), how would we get an accurate initial value, if we weren't notified of those between-gesture changes?

Back to Bug 1916010 Comment 4