Closed Bug 683380 Opened 15 years ago Closed 15 years ago

Clicking a refresh after navigating back from filtered search results, results in a page without CSS (unstyled)

Categories

(addons.mozilla.org Graveyard :: Add-on Builder, defect, P2)

defect

Tracking

(Not tracked)

VERIFIED WORKSFORME
Builder 1.0

People

(Reporter: stephend, Assigned: aschaar)

References

()

Details

This is a _tad_ pathogenic, but still should work. Screencast: http://screencast.com/t/krWs0MkBKp STR: 1. load https://builder-addons.allizom.org/search/?type=a&author=4 2. click on Combined: https://builder-addons.allizom.org/search/?author=4 3. now click on See all 6… : https://builder-addons.allizom.org/search/?type=a&author=4 4. now, click Back, and do a refresh Actual Results: You get a page without CSS
And there's an exception: Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWebNavigation.sessionHistory]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: :: line 663" data: no] Source File: chrome://global/content/bindings/browser.xml Line: 670
It would almost seem like the browser caches the result from the Ajax request, and then the refresh loads the snippet from the cache. To test this, I added an extra param to the url for the Ajax requests, such that the actual URL shouldn't be cached, just the XHR version: https://github.com/mozilla/FlightDeck/commit/63a8620a52d9d3c361fab19bfdc71afa38c8bef7 However, Stephen says that it still does not work, though a _hard_ refresh does, lending some more credibility that it _is_ hitting the cache... but it's not...
Summary: Clicking a hard refresh after navigating back from filtered search results, results in a page without CSS (unstyled) → Clicking a refresh after navigating back from filtered search results, results in a page without CSS (unstyled)
Arron, if you can reproduce this, please investigate and advise. Stephen, are you still seeing this?
Assignee: nobody → aschaar
Priority: -- → P2
Target Milestone: --- → Builder 1.0
If I recall, this was a a Firefox push/popstate bug. Perhaps it's been resolved in Firefox?
Can't reproduce it.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Verified WFM using the Firefox nightly; I think we fixed this along the way, obviously. Thanks for trying, Arron!
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.