Add information about whitespaces text nodes #28177
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I was thinking that maybe adding something similar to the Node documentation could be useful as well. What do you think about that? |
sideshowbarker
approved these changes
Jul 26, 2023
|
Preview URLs |
|
Thiago, thanks much, and congrats on landing your first docs change here — welcome aboard 🎉 |
That’d be great, yes |
|
Alright, thanks for the feedback ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I added some information about empty text nodes in the
Node.childNodesdocumentation, with a reference to a documentation about the subject.This was inspired by the notes in the previousSiblings and nextSiblings pages.
Motivation
I got myself pretty confused when trying to find out why
childNodeswas returning an array full of empty text nodes, and took me a while to find a reference to this very helpful docs that made things clearer for me. I think other people could use this reference in the future when faced with a similar problem.