option to cache or not cache a "sub-page" #1471
Description
Perhaps this already exists or there is some workaround for what I am trying to do, but I am not sure, hence the issue log :)
In my very simple web app all I have on the initial page is a list of my friends and let's say I have 40 and each list item has a link in the following structure:
or
- /profile/2/
- /profile/3/
..
If a user browses 10 of his friends there are now 10 "sub-pages" that have been dynamically added. At what point does the DOM become too bloated so that performance is affected? What if I viewed 100 friends?
In order to manage that bloat, would it make sense to provide a an optional attribute called "data-cache-page" so that if set to false, once the page becomes inactive (i.e transitioned out of the viewport) it is removed from the dom?
Something like
Another example where I might not want a page to be cached is if the user looks at a friends profile in the morning and then returns to the profile at night. I would like for that user to see the non-cached version of that page/div.