Pierre-Yves Gérardy

@isiahmeadows couldn’t we rather hardcore the version number in a small script that would be generated on release by our npm script?

I mean this (but I may be missing your intent). ```HTML The latest version is v ``` ```JS // latest.js mithrilVersion.textContent = "x.y.z" ```

Now this makes complete sense, thanks for clarifying.

It is called DOM hydration, and it would need explicit support. I was looking into it last autumn before being side tracked by the router.

Alternatively, while hydrating, if you encounter several consecutive text vnodes, you can turn them into a fragment of textNodes and replace the textNode in the DOM with it. Empty text...

As an alternative, if you don't need this fixed for ivi, a source comment about the quirk could be nice. I can change this PR accordingly if you want. Edit:...

I'd say, go with whatever fix makes the most sense for `ivi`, and document the quirks, if any? I don't think the `-2` trick would work for what I do...

Another way to tackle this would be to make a new kind of mindful fragments (by contrast to the current amnesiac ones). ```JS const frag = document.createDocumentFragment() frag.mindful = true...

This is related to moving keyed lists of fragments, but it may actually be an X/Y question, as I'm still processing the DOM 4 methods. I probably posted too soon,...

So you'd suggest scraping `FutureFeatures.md` (replacing it with a stub, because LinkRotSucksTM), and updating the corresponding links elsewhere in these docs?