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 has been archived by the owner on Dec 19, 2024. It is now read-only.
As it is right now, iron-pages doesn't provide for a way to destroy non-currently viewed pages and restamp them when they come back into view.
Providing a property that does this (perhaps restamp), would allow for significant performance improvements when navigating through complex DOM chunks with multiple levels of nested iron-pages.
There's potential hacks around this using <dom-if> but they don't really scale well for many subpages and they result in convoluted markup, see this S.O question
The text was updated successfully, but these errors were encountered:
I have just pushed support for dom-if in iron-lazy-pages. The implementation is rather naive: just mimic the if property to the selected/deselected to trigger the dom-if restamping. Check it out at TimvdLippe/iron-lazy-pages#56
As it is right now,
iron-pages
doesn't provide for a way to destroy non-currently viewed pages and restamp them when they come back into view.Providing a property that does this (perhaps
restamp
), would allow for significant performance improvements when navigating through complex DOM chunks with multiple levels of nested iron-pages.There's potential hacks around this using
<dom-if>
but they don't really scale well for many subpages and they result in convoluted markup, see this S.O questionThe text was updated successfully, but these errors were encountered: