Andrea Giammarchi

FWIW this is apparently a very demanded feature from the Web Developers community Previously on a similar proposal: https://discourse.wicg.io/t/proposal-live-fragments/2507

As simplified approach, and for demo sake, I'll leave a playground that works out of the box in Chrome Canary (but not yet in Code Pen, however I've informed them...

@annevk just FYI I think there's a typo in the title: _onse_ => _once_ also, if I might ask, what does the label "_needs implementer interest_" mean? What can I...

Nothing is kept in the DOM. It's a fragment that acts like a fragment. I'm working on a better playground that shows the idea fully polyfilled so please wait for...

So, I've uploaded the previously mentioned polyfill, which should have 100% code coverage. https://github.com/WebReflection/document-persistent-fragment There is a [live test page](https://webreflection.github.io/document-persistent-fragment/) too. ### the what The idea is to have a...

@rniwa FYI I've [filed the bug](https://bugs.webkit.org/show_bug.cgi?id=195556) that makes current polyfill ~~not usable~~ * in WebKit/Safari **edit** I've fixed the current polyfill with a workaround after a feature detection, so this...

@rniwa I've no idea what is this `NodeTemplatePart` and I cannot find anything online, however, if you would read at least the [test](https://github.com/WebReflection/document-persistent-fragment/blob/master/test.js#L26) you'll see this proposal is literally nothing...

@justinfagnani > Edit: I didn't see that in this version of the idea the fragment doesn't live in the tree. would you mind amending/canceling that comment since nothing in there...

> you'd have persistent fragments in persistent fragments which is fine, and since appending a fragment to itself breaks, there's nothing different on the DOM. Current implementation / proposal allows...

Hey @vitaly-t, how is that related to this proposal?