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

Sugaring dynamics in ShadowDOM #176

Closed
sjmiles opened this issue Jun 7, 2013 · 3 comments
Closed

Sugaring dynamics in ShadowDOM #176

sjmiles opened this issue Jun 7, 2013 · 3 comments
Assignees

Comments

@sjmiles
Copy link
Contributor

sjmiles commented Jun 7, 2013

Polymer sugaring, including event processing, data binding, and node marshalling, only happens once at shadow DOM creation time.

As there may be use cases where users want to update/replace shadow DOM and still have sugaring, we probably should provide an API for doing this imperatively.

Here is an example of some code that could be used, in particular, for managing MDV bindings on shadow DOM replacement.

http://jsfiddle.net/xkV5q/3/

@ebidel
Copy link
Contributor

ebidel commented Jun 7, 2013

cc @ebidel

@warpech
Copy link

warpech commented Jun 14, 2013

+1

@ghost ghost assigned sorvell Sep 25, 2013
@sorvell
Copy link
Contributor

sorvell commented Aug 14, 2014

This is now pretty easily done by just making a template and calling instanceTemplate:

http://jsbin.com/menero/1/edit

This is pretty flexible and seems like it doesn't need much improvement. The only thing missing in this case is node marshaling (which can be manually addressed by calling marshalNodeReferences(root)). Since that issue is separately addressed, closing this issue.

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

4 participants