Skip to content

Commit cc298bc

Browse files
committed
Updated README.md
1 parent 857ffac commit cc298bc

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,11 @@ JSX is not part of this library natively, but a wrapper can be made quite easily
229229
So at `0.2.0` I made it so that all children of the `ParentNode` updates when a `Signal` child changes. Tho this issue can be escaped by
230230
seperating things while writing the code. Or make use of things like `.replaceChild()`. Since all support `Signal`(s) now.
231231

232-
But to solve the core of this issue JS needs a real `DocumentFragment` with persistent children.
232+
You might be saying "Why not just use comment nodes?": Yes, creating ranges with comment nodes is the traditional solution to this issue.
233+
But it's not a native ranging solution, and the frameworks that use it break as soon as you mutate the DOM without the framework, which is
234+
against the philosophy of the library.
235+
236+
So to solve the core of this issue JS needs a real `DocumentFragment` with persistent children.
233237

234238
This proposal might solve this issue:
235239
[DOM#739 Proposal: a DocumentFragment whose nodes do not get removed once inserted](https://github.com/whatwg/dom/issues/736).

0 commit comments

Comments
 (0)