Closed Bug 989971 Opened 11 years ago Closed 11 years ago

"More" search results aren't still available when hitting back.

Categories

(Marketplace Graveyard :: Consumer Pages, defect, P2)

Avenir
x86
macOS
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
2014-04-01

People

(Reporter: muffinresearch, Assigned: cvan)

Details

(Keywords: regression)

STR: * Go to -dev marketplace * From homepage scroll to bottom of results * Click more * Scroll down and click the details page of the app noting the scroll position. * From the details page hit the back button in the app What happens: * You end up at the bottom of the first page of results (with the more button visible) What should happen: * You should return to the point in the page where you were when you clicked through to the details page. This used to work and the previous results page complete with the extra content loaded via the "more" button used to be available.
Doesn't happen on prod
Bisecting the commits points to https://github.com/mozilla/fireplace/commit/076871afe6109c111a5f8227b0c52bbcec9c4372 being the commit that introduced this issue.
(In reply to Stuart Colville [:scolville] from comment #2) > Bisecting the commits points to > https://github.com/mozilla/fireplace/commit/ > 076871afe6109c111a5f8227b0c52bbcec9c4372 being the commit that introduced > this issue. Are you positively sure that's the right commit? I would think it'd be https://github.com/mozilla/fireplace/commit/51c372a0 but I haven't bisected myself. Thanks for catching this, Stuart. I really do wish we caught this way earlier in the week though :\
Priority: -- → P2
(In reply to Christopher Van Wiemeersch [:cvan] from comment #3) > (In reply to Stuart Colville [:scolville] from comment #2) > > Bisecting the commits points to > > https://github.com/mozilla/fireplace/commit/ > > 076871afe6109c111a5f8227b0c52bbcec9c4372 being the commit that introduced > > this issue. > > Are you positively sure that's the right commit? > > I would think it'd be https://github.com/mozilla/fireplace/commit/51c372a0 > but I haven't bisected myself. > > Thanks for catching this, Stuart. I really do wish we caught this way > earlier in the week though :\ I agree. https://bugzilla.mozilla.org/show_bug.cgi?id=983815 was marked as [qa-]. So, I won't feel too terrible about it :)
based on those commits, I assume -> cvan
Assignee: nobody → cvan
https://github.com/mozilla/fireplace/commit/39c270a My bad - forgot about the "More results" button. When you clicked the "More results" button, fireplace already had the model data in the model cache, so it didn't even try to fetch the XHR from the request cache. But when you navigated away and came back, fireplace tried to use the request cache, and because the "More Results" button was pointing to our API instead of our CDN for the results, fireplace got confused and gave up. Thanks, everyone!
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2014-04-01
Issue is still reproducing in https://marketplace-dev.allizom.org/ on FF31 (Win 7) and MP-dev app (FF OS). Scroll is not preserved after going back from app details page. Please see screencast for Win 7 http://screencast.com/t/wdxB7oEG4
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to Iulian Timis from comment #7) > Issue is still reproducing in https://marketplace-dev.allizom.org/ on FF31 > (Win 7) and MP-dev app (FF OS). > Scroll is not preserved after going back from app details page. > Please see screencast for Win 7 http://screencast.com/t/wdxB7oEG4 It's working for me in Nightly OSX and FFOS 1.2 Inari.
I'm also doing exactly what you're doing in the screencast and I cannot reproduce. Can you make sure you refreshed the assets in your browser? I don't know what to say. Can you try again?
I have tried on a new profile but I was not able to reproduce http://screencast.com/t/z40rbXqilw It's working properly on FF OS also.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.