minor
This commit is contained in:
parent
3ce2d96948
commit
7d6d4366a3
5 changed files with 34 additions and 28 deletions
|
@ -1,4 +1,6 @@
|
|||
1. Yes, true. The element `elem.lastChild` is always the last one, it has no `nextSibling`, so if there are children, then yes.
|
||||
2. No, wrong, because `elem.children[0]` is the first child among elements. But there may be non-element nodes before it. So `previousSibling` may be a text node.
|
||||
1. Yes, true. The element `elem.lastChild` is always the last one, it has no `nextSibling`.
|
||||
2. No, wrong, because `elem.children[0]` is the first child *among elements*. But there may exist non-element nodes before it. So `previousSibling` may be a text node. Also, if there are no children, then trying to access `elem.children[0]`
|
||||
|
||||
Please note that for both cases if there are no children, then there will be an error. For instance, if `elem.lastChild` is `null`, we can't access `elem.lastChild.nextSibling`.
|
||||
Please note: for both cases if there are no children, then there will be an error.
|
||||
|
||||
If there are no children, `elem.lastChild` is `null`, so we can't access `elem.lastChild.nextSibling`. And the collection `elem.children` is empty (like an empty array `[]`).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue