0
Answered

Fetching Character / Fetching Results happens on back - Why? No caching?

Psy Draggy 4 years ago updated by Digby (Community Manager) 3 years ago 1

I noticed while navigating through the site and getting used to the layout that FN appears to completely ignore browser caching.

If I'm clicking through a user's gallery to view their submissions it refreshes each and every time I click back, displaying the "Fetching Character" or "Fetching Results" notification. I could just open everything in a new tab, but that's not the point of this question.


I get that there's an advantage to always pulling the latest information, but I would argue the disadvantages outweigh the advantages in this case, at least for user galleries. The front page is the only place I can think a lack of browser caching would be arguably useful.

Beyond the increased data usage, it creates an extremely sluggish user experience.

Thinking on this more I think I even have an idea to post... but this question still stands.


Putting this in Questions instead of Bugs as I'm guessing it's a conscious decision.

Answered

We've looked at making the site efficient for users. A big reason for images being removed when browsing elsewhere is to improve site stability; when too many images are on a page, it lags and sometimes crashes. There are advantages and disadvantages to the way that our development team has worked to create stability, but this has been reliable so far.