Created attachment 8666053 [details] video1.mp4 Steps to reproduce: 1. Make sure you have History populated 2. Go to History panel and tap on Today section 3. Scroll down the list 4. Tap on Yesterday section and observe the scroll position Expected result: On the Yesterday section, the history entries on the right are in the initial position Actual result: The history entries for Yesterday section, are scrolled exactly the same position as the Today section (see attached video)
Mentor: firstname.lastname@example.org, email@example.com
Whiteboard: [lang=java][good first bug]
I suggest to add ``` mList.smoothScrollToPosition(0); ``` in the item click listener. I am currently browsing the docs how to submit a patch...
Created attachment 8669472 [details] Screen record of proposed solution device-2015-10-04-225729.mp4
Hi there and welcome! :) (You might want to set a name or nickname in your bugzilla profile) (In reply to mail from comment #1) > I suggest to add > ``` > mList.smoothScrollToPosition(0); > ``` > > in the item click listener. I am currently browsing the docs how to submit a > patch... I like it! Are you using Mercurial? Here's a guide on how to create a patch: https://developer.mozilla.org/en-US/docs/Mercurial/Using_Mercurial#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F If you need more help: You can find me (sebastian) and other helpful people in #mobile on irc.mozilla.org. For IRC setup instructions, see https://wiki.mozilla.org/IRC
Assignee: nobody → mail
Created attachment 8669900 [details] [diff] [review] fix with smooth scrolling (friedger.patch) patch attached using smooth scrolling
Comment on attachment 8669900 [details] [diff] [review] fix with smooth scrolling (friedger.patch) Review of attachment 8669900 [details] [diff] [review]: ----------------------------------------------------------------- LGTM. Thanks!
Attachment #8669900 - Flags: review?(s.kaspari) → review+
I received an automated email to get the patch checked in. I thought I follow the required steps. Is there anything left I need to do? Thanks for the mentoring :-)
(In reply to friedger from comment #6) > I received an automated email to get the patch checked in. I thought I > follow the required steps. Is there anything left I need to do? Oh, sorry! I should explain the next steps. Especially as one of them has to be triggered by me. :) So, the next steps are: 1. Push the patch to try. The try server will build the app and run some tests, depending on configuration. This will require hg level 1 access, so I'll do it for you in a second and post the link here. 2. If everything is green on try then add the checkin-needed keyword to this bug. Someone with hg level 3 access will come along and commit and push your patch. 3. Your change will land in fx-team and then be merged from there to mozilla-central. After that it will show up in the next Nightly builds. :) For future patches add "r=name" (in this case: r=sebastian) to the commit message to identify who reviewed the patch. But in this case the friendly person commiting and pushing the patch will add it. :)  https://wiki.mozilla.org/Build:TryServer  https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/  http://hg.mozilla.org/integration/fx-team  https://hg.mozilla.org/mozilla-central/  https://nightly.mozilla.org/  https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Committing_Rules_and_Responsibilities#Commit_message_restrictions
(In reply to Sebastian Kaspari (:sebastian) from comment #8) > Here we go: > https://hg.mozilla.org/try/pushloghtml?changeset=fb72037abd21 I just realized I posted the pushlog. :-) This is the link to follow the progress: https://treeherder.mozilla.org/#/jobs?repo=try&revision=fb72037abd21
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox44: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 44
Marking this as Verified, since there is a follow up bug 1213760 for this issue
Status: RESOLVED → VERIFIED
status-firefox44: fixed → verified
You need to log in before you can comment on or make changes to this bug.