You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 8, 2021. It is now read-only.
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:
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.
The text was updated successfully, but these errors were encountered:
there was supposed to be an html example after "Something like..." but I see the html is stripped. Hopefully the preceding paragraph should suffice in illustrating my proposal.
This is definitely something that needs to be worked on. I've been having this issue myself and have no idea how to prevent the page being "cached" without losing the back functionality & transitions.
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
..
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.
The text was updated successfully, but these errors were encountered: