Skip to content

feat: clarify point in dom-navigation article.md en #3919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open

front42 wants to merge 1 commit into javascript-tutorial:master

from front42:patch-7

Open

feat: clarify point in dom-navigation article.md en #3919

Changes from all commits

Commits

Show all changes

Select commit

feat: clarify point in dom-navigation article.md en

front42 Jan 2, 2026

File filter

Filter by extension

Conversations

Jump to

Jump to file

Failed to load files.

Loading

Diff view

Diff view

2 changes: 1 addition & 1 deletion 2-ui/1-document/03-dom-navigation/article.md

Show comments View file Open in desktop

Original file line number	Diff line number	Diff line change
Expand Up		@@ -163,7 +163,7 @@ Changing DOM needs other methods. We will see them in the next chapter.
		```warn header="DOM collections are live"
		Almost all DOM collections with minor exceptions are live. In other words, they reflect the current state of DOM.

	If we keep a reference to `elem.childNodes`, and add/remove nodes into DOM, then they appear in the collection automatically.
	If we keep a reference to `elem.childNodes`, and add/remove nodes in the DOM, then they will automatically appear in the collection -- or be removed from it.
		```

		````warn header="Don't use `for..in` to loop over collections"
Expand Down