Just noticed this when I added the Pocket list. When loading an article, the reader toolbar appears in the wrong position, and then snaps into place. I made a little movie about it: http://cl.ly/2f0K150q0D2W This does not seem to happen when opening an article in Reader from the toolbar icon. Just about:home.

Leaving as a nom until we have a regression window

Regression window-wanted: 1.mozilla central: not affected build: 16-12-2013 affected build: 17-12-2013 -pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0d11fce4f845&tochange=b1e5ade62913

It would be nice if someone from the mobile platform/graphics team had a look at this range. Brad, does anything stand out as the potential offender here?

I'm able to reproduce this on a local build from 0d11fce4f845 as well, so I don't think the regression window is correct. Or perhaps it just became more obvious during that window? The STR I'm using: 1. Go to https://staktrace.com/spout/, switch to reader mode, add it to the reading list, and close the tab (you can skip this if you've already done it and are just testing a new build) 2. From about:home, swipe over to the reading list, and open the above-added entry. Wait for it to fully load 3. Go back to about:home and load something else (in my case I just used a thumbnail tile of file:///sdcard/) 4. Go back to about:home and load the reading list entry again. This time I see the toolbar jump

But yeah, I can't reproduce on the Dec 16 nightly build either. Maybe a race condition that always triggers in debug builds, but only showed up Dec 17 nightly release.

filter on [mass-p5]

Reproducible when opening a page from Reading List panel: the reader mode toolbar appears in the wrong position for a few seconds and then is positioned at the bottom.

After Bug 998031 - Reader Mode toolbar should scroll in and out instead of fading was introduced, when opening a page from the reader mode panel, a grey bar is displayed before the reader mode toolbar slided off the screen. I filled Bug 1145567 for this.

I can't reproduce this any more. Please reopen if you can. The underlying issue is probably the same as in bug 1148391 which was fixed by bug 1180295.