Ian Clarke

No problem, I'm going to leave this open to investigate why the singleton plugins were causing problems.

Requiring a wrapper element like the `` for `render {}` was kinda a kludge from the start, to make it easy to replace the rendered content when the `KVar` updates,...

I think if we reuse the same `ElementCreator` then it should be reset to the state it would have been in with no elements before we add any new elements,...

It should be possible to make this improvement without sacrificing speed. Currently we can just call [Element.removeChildren()](https://github.com/kwebio/kweb-core/blob/master/src/main/kotlin/kweb/Element.kt#L208) on the wrapper ``, which lets the browser do the work of figuring...

Yeah, getting element replacement right in situations where there are sibling elements that are not part of the `render {}` block is the headache that prompted the `` solution in...

Note: version 0.7.19 doesn't yet eliminate the need for a container element, but it does allow you to change the type of element used with `render(containerElementTag = "li") { .....

Not right now I'm afraid, I could add another parameter to `render` to support configuration of the container element - although this would just be a stop-gap until we can...

Good point, just released `0.7.20` which supports this: ```kotlin render(container = { li().classes("item") }, value = v) { ... } ``` (The reason I'm not allowing a raw `Element` to...

Yes - that would probably work with the current implementation - so I guess it was inaccurate to say it would *ensure* use of the parent ElementCreator, but it would...

Relevant for appending multiple elements: * https://johnresig.com/blog/dom-documentfragments/ * https://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-B63ED1A3 * https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ms766442(v=vs.85) Notes: * ElementCreator should be able to add elements to a DocumentFragment rather than just a parent element. *...