tarako build identifier: 20140331101634 connectivity used: EDGE noticed on: dev (latest build) app used for test: Pathuku steps to reproduce: 1. Launch the latest marketplace-dev packaged app 2. Go to any category and scroll down(I scrolled down to the bottom of the page in order to highlight the scroll position difference) 3. Open any app and then press back button expected behavior: Scroll position is retained after hitting back button observed behavior: Scroll position is not retained reproducible?: Yes ashes: behavior seen on regular marketplace using inari/hamachi: yes/no Screencast with position before opening the app: http://screencast.com/t/clVjgIorOln Screencast with position after pressing back button: http://screencast.com/t/zxouENqNj

Can anyone else reproduce? Works for me in browser + simulator, and the code for that hasn't changed.

Is this the same as bug 990525?

Fwiw: All these scrolling issues tend to only show-up on device. So you'll probably find in-browser/emulator testing won't reproduce them. To solve these scroll issues properly we could really do with some kind of event that we can hook into that fires once all parts of a page have been rendered. The main issue is that during rendering the page length is in a state of flux and as a result requesting a specific scroll position during this time can result in the position being incorrect including asking for the top of the page. I'm not sure such an event readily exists within fireplace that amounts to all parts of a page have been rendered. There's the request pool but and you can listen for when all requests have returned but afaik there's not something that ties together the subsequent rendering based on the data from those requests. Happy to chat about it with anyone if that would help.

We could use something like fragment_loaded, otherwise yeah we'll have to check that all fragments are loaded somehow.

This is a rabbit-hole we won't go down for v1.