You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Framework/framework-en.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -294,12 +294,12 @@ ul.childNodes[2].remove()
294
294
let fromNode =ul.childNodes[4]
295
295
let toNode =node.childNodes[3]
296
296
let cloneFromNode =fromNode.cloneNode(true)
297
-
letcloenToNode=toNode.cloneNode(true)
297
+
letcloneToNode=toNode.cloneNode(true)
298
298
ul.replaceChild(cloneFromNode, toNode)
299
-
ul.replaceChild(cloenToNode, fromNode)
299
+
ul.replaceChild(cloneToNode, fromNode)
300
300
```
301
301
302
-
Of course, in actual operations, we need an indentifier for each node, as an index for checking if two nodes are identical. This is why both Vue and React's official documentation suggests using a unique identifier `key` for nodes in a list to ensure efficiency.
302
+
Of course, in actual operations, we need an identifier for each node, as an index for checking if two nodes are identical. This is why both Vue and React's official documentation suggests using a unique identifier `key` for nodes in a list to ensure efficiency.
303
303
304
304
DOM element can not only be simulated, but they can also be rendered by JS objects.
305
305
@@ -393,7 +393,7 @@ We then have two steps of the algorithm.
393
393
394
394
First let's implement the recursion algorithm of the tree. Before doing that, let's consider the different cases of comparing two nodes.
395
395
396
-
1. new nodes's `tagName` or `key` is different from that of the old one. This menas the old node is replaced, and we don't have to recurse on the node any more because the whole subtree is removed.
396
+
1. new node's `tagName` or `key` is different from that of the old one. This means the old node is replaced, and we don't have to recurse on the node any more because the whole subtree is removed.
397
397
2. new node's `tagName` and `key` (maybe nonexistent) are the same as the old's. We start recursing on the subtree.
398
398
3. no new node appears. No operation needed.
399
399
@@ -403,10 +403,10 @@ import Element from './element'
0 commit comments