Closed Bug 1037576 Opened 10 years ago Closed 9 years ago

Implement CSS scroll nudging

Categories

(Firefox OS Graveyard :: Gaia::Homescreen, defect, P2)

x86
macOS
defect

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: gbrander, Unassigned)

References

Details

(Whiteboard: [systemsfe][priority])

Meta for CSS scroll nudging. The original design work for the vertical homescreen involved scroll nudging as an improvement to the ergonomics of scrolling. Once we have platform-level smooth-scrolling, we would like to implement this. Timeline TBD depending on risk and GFX timeline.
Depends on: 1022818
No longer depends on: 977967
Adding bug 964097 in the dependency chain as we seem to have two bugs tracking this work.  Oh, and it's a layout feature, they get the credit for the awesomeness in the end.
Depends on: 964097
blocking-b2g: --- → backlog
Whiteboard: [systemsfe][priority]
Bug 945584 Comment 62 describes how the CSS scroll-snapping feature could be completed, with integration of momentum and smooth transitions from fling gestures.

Alternately, Bug 964097 (CSSOM-View scroll-behavior) spec adds smooth scrolling which together with GAIA side scripting could implement the scroll nudging effect.  Earlier UX + GFX standup meetings have revealed that it would also be necessary to expose either the velocity of the fling gesture or the predicted landing position of the fling gesture.

Please review and advise if this would be best implemented with Bug 945584's redux or if we should expose more information from the fling gesture to implement it on the GAIA side on top of the CSSOM-View scroll-behavior extensions.
Flags: needinfo?(kgrandon)
CSSOM-View scroll-behavior will provide many other benefits besides only declaritive scroll snapping in gaia. I am open to trying to implement scroll-snapping using this approach initially, though I'm not 100% sure if this will work as well as we would expect.

To do so we would definitely need some more information for gaia in the form of some kind of event or API that tells us the expected ending position. I sent out an email about this recently to a few folks and forgot to add you, but perhaps it's time to bring that discussion to a bug or mailing list.
Flags: needinfo?(kgrandon)
Priority: -- → P2
blocking-b2g: backlog → ---
Mass update: Resolve wontfix all issues with legacy homescreens.

As of 2.6 we have a new homescreen and having these issues open is confusing. All issues will block bug 1231115 so we can use that to re-visit any of these if needed.
Blocks: 1231115
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.