Closed Bug 1213760 Opened 6 years ago Closed 9 months ago

Scroll refresh action should not be visible when switching calendar section

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox44 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox44 --- affected

People

(Reporter: u549602, Unassigned, Mentored)

References

Details

(Whiteboard: [lang=java])

Sony Xperia Z2 (Android 5.0.1)
Nightly 44.0a1

Steps to reproduce:

1.Make sure there's browsing history in two different calendar history sections
2.Scroll down in one calendar section (e.g Today)
3.Tap on another calendar section (e.g Yesterday)

Actual results:
The second visited calendar section is refreshed (scroll up action to top of the list) even though this section has not been scrolled before
Each calendar section is scrolled to top of the list when accessed no matter the previous scrolling history in that section

Expected results:
Each calendar section scroll should be independent and no scroll refresh should be displayed 

For further details please check https://youtu.be/wbgn0-VrnIE
This scroll has been introduced on purpose in bug 1208519 (smoothScrollToPosition()).

Is it more the scrolling animation that you think we should omit. Or do you think we should remember and restore the scroll offset for every section?
Mentor: s.kaspari
That initial bug ( 1208519 ) was submitted because the scroll position was the same in all sections no matter in which calendar time period the scroll action was performed.
Even with the pushed fix, it can be noticed that the scroll is still performed simultaneously in all sections when the user scrolls in a focused one. 

The difference is that when the user visits a new section, the browsing history is scrolled up to the top of the list with a visible confusing effect. If the desired behavior is to reset the scroll position at every new section access then the refresh action should be performed in the background(for the non focused section) after the user changes focus on a new calendar section.
Okay, makes sense. Resetting the scroll position without an effect is definitely easier and easier to maintain than keeping all the different positions per section.

Friedger, do you want to have a look at this?
Flags: needinfo?(mail)
We can use `mList.setSelection(0);` 
Currently, there is no way to refresh/reset the scroll position in the background. Technically, there is only one list that is used to show the different sections.

We could introduce loading animation or so to get a better/less confusing UX.
Flags: needinfo?(mail)
(In reply to friedger from comment #4)
> We can use `mList.setSelection(0);`

I think that's the way to go.

(In reply to friedger from comment #4)
> Currently, there is no way to refresh/reset the scroll position in the
> background. Technically, there is only one list that is used to show the
> different sections.

We could keep and restore the scroll position ourselves but I don't think it's worth the effort.

(In reply to friedger from comment #4)
> We could introduce loading animation or so to get a better/less confusing UX.

Do you think setSelection() is confusing or are you thinking about animations as an alternative to using setSelection()?
Whiteboard: [lang=java]
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.