Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow restamping #53

Open
nicholaswmin opened this issue Dec 9, 2016 · 4 comments
Open

Allow restamping #53

nicholaswmin opened this issue Dec 9, 2016 · 4 comments

Comments

@nicholaswmin
Copy link

nicholaswmin commented Dec 9, 2016

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

@Boscop
Copy link

Boscop commented Feb 18, 2017

+1 for this!
Btw, I found this related blog post:
http://nader.tn/2015/07/polymer-element-recreation/

@JunedS
Copy link

JunedS commented Feb 25, 2017

+1
Missing this feature very much.
Btw, I found this https://github.com/TimvdLippe/iron-lazy-pages built on top of iron-pages
Why cant the same be implemented in iron-pages?

@TimvdLippe
Copy link

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

@tandacedric
Copy link

Do like this
image
Do not forget to put the "div" because iron-page needs that to manage
and create equal fonction in your script like this
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants