Tomek Wytrębowicz
Tomek Wytrębowicz
As HTML Imports are dying there is a new proposal for a spec being discussed https://github.com/w3c/webcomponents/issues/645 Hopefully, we will be able to adapt our solution to the new spec once...
see discussion at https://github.com/Juicy/imported-template/pull/56#issuecomment-390980670 ### Steps to reproduce 1. Go to https://github.com/Juicy/imported-template/blob/master/imported-template.html#L172 It hacks Polymer notification protocol to forward `partial, viewModel` even though we only use `model`. Removing them seems...
Currently when another `` instance for same url is attached to DOM we create new `` element. Luckyli it does not hit the networking performance, as according to HTML Imports...
Currently once attached `` stamps imported content into DOM. We could apply Polymer's convention and does not stamp a thing, untill `.model` property gets attached, or if and attribute is...
So we could in fact nest imported partial into client template: ``` html Partial is already loaded ``` Which will produce same result as: ``` html Partial is already loaded...
It seems I implemented https://github.com/Juicy/imported-template/commit/f33a5df8988773a1ffb2588fc6e91b8a8bc7cfb4 incorrectly. It fires an event `stamped` once `link` is appended to the tree so far before content is actually stamped to the tree. I believe...
### Steps to reproduce 1. Create `imported-template` using `` ```html ``` 2. Attach a model `domBind.set('model', {foo: 'not changed'});` and import scopeless document: ```html {{model.foo}} ``` 3. Change `foo` property...
Currently we do all the work (importing, fetching and stamping elements, attaching the model) on `attachedCallback`. What if we: 1. Import nodes on `createdCallback` and every content `attributeChangeCallback` even when...
or change master branch to gh-pages, and add `/index.html` as demos for specific elements are already there :)
(This is a follow up from https://github.com/woocommerce/pinterest-for-woocommerce/pull/308#discussion_r774489991) ### Is your feature request related to a problem? Our files structure grown, and som imports uses paths like: `import { REPORTS_STORE_NAME }...