-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Fix DOM nesting on the Storage page dialogs, enable DOM nesting errors #19509
Conversation
2a0e10f
to
f8bf272
Compare
After round 1: The ListingTable nesting fix caused some test regressions, selectors need to be adjusted. Some of the storage failures are also due to that, and some are independent problems. /expensive and /networking are green now. |
f8bf272
to
28ebf95
Compare
28ebf95
to
6e7b9fa
Compare
6e7b9fa
to
94ae7a2
Compare
A `<table>` must not appear inside of a `<p>`, make them siblings instead.
A `<List>` block element must not appear inside a `<p>`, make them siblings instead.
RemovePassphraseField is already in a `<Form>`, so don't wrap the checkbox into a second one.
A ClipboardCopy is a block element (`<div>`) and thus cannot be put into a `<p>`. Make them silblings. To retain the current layout, turn the text into a simple span, so that the text and the ClipboardCopy still appear side by side.
Most errors were fixed recently. The remaining ones on the Storage page conflict with the ongoing page redesign, and may well already be fixed by it. Ignore them specifically for now. This will prevent introducing new DOM nesting errors in the future.
94ae7a2
to
c71e152
Compare
<Checkbox id="force-remove-passphrase" | ||
isChecked={val !== false} | ||
label={_("Confirm removal with an alternate passphrase")} | ||
onChange={(_event, checked) => change(checked ? "" : false)} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This added line is not executed by any test. Details
Rawhide failure is unrelated, see PR #19525 |
We have the following cases in main:
storage:
expensive/networking already got fixed in #19520:
/other is okay.
Builds on top of: