Skip to content

Commit a24fc70

Browse files
committed
Updated README.md to add update
1 parent de858f4 commit a24fc70

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -222,6 +222,11 @@ JSX is not part of this library natively, but a wrapper can be made quite easily
222222
So, in version `0.2.0`, I made it so that **all children** of a `ParentNode` update when a `Signal` child changes. This issue can be
223223
managed by structuring code carefully or using `.replaceChild()`, since all nodes now support `Signal`(s).
224224

225+
---
226+
**UPDATE:** Switched back to using `<div>` with `display:contents`.
227+
228+
---
229+
225230
Some might ask, _"Why not just use comment nodes?"_ Yes, using comment nodes for tracking ranges is a traditional solution. But it’s not
226231
**a native ranging solution**, and frameworks that rely on it **break if the DOM is mutated manually**, which goes against this library’s
227232
philosophy.

0 commit comments

Comments
 (0)