Add better explanation on when to use PanelRow #60515
Open
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.
What?
Adds better explanation on when to use a
PanelRowcomponent and when not.Why?
In #41671 it was mentioned (comment), that using a PanelRow for single components is not necessary / may have side-effects. For example some inputs may not render as expected, since they are flex-children. For my self, the documentation suggested, that the structure should always be
Panel>PanelBody>PanelRow. I think it may make sense, to explicitly state, that using a PanelRow is not necessary.Here's a screenshot showing the difference:
PanelRow is a flex-child and adds margin-top.

Open Questions
The markdown file in question has some linting errors: missing image alt texts and especially duplicate heading ids. Is there a rule on how to avoid duplicate heading ids if the headings are the same (
Usage)?How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast