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

External script support #6

Closed
tomalec opened this issue Mar 20, 2014 · 1 comment
Closed

External script support #6

tomalec opened this issue Mar 20, 2014 · 1 comment

Comments

@tomalec
Copy link
Member

tomalec commented Mar 20, 2014

As for now all external <script src="files.js"> children of loaded content are removed, and not loaded/executed back again (as they have no .textContent).

But, when loaded dynamically (for example via <template>) they works fine.

Are they removed in purpose? Can't just remove and execute pragmatically script:not([src]) ones?


However, if we would like to do so, it would be nice to make sure both inline and external scripts are loaded/executed in correct order.

tomalec added a commit that referenced this issue Mar 25, 2014
…del binding (#7) out of the box,

binding model scope to the `x-html` does not require wrapping in additional `<template>`,
delegate handling scripts, styles, and imports handling (#6, #3) to HTML Template Element,
and get nice content-as-sibling support with almost no effort,
@tomalec
Copy link
Member Author

tomalec commented Apr 29, 2014

Now <script> and <style> tags are handled by <template> itself without any magic from x-html. For more sophisticated cases use PuppetJs/imported-template.

@tomalec tomalec closed this as completed Apr 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant