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
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.
The text was updated successfully, but these errors were encountered:
…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,
Now <script> and <style> tags are handled by <template> itself without any magic from x-html. For more sophisticated cases use PuppetJs/imported-template.
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.
The text was updated successfully, but these errors were encountered: