Use generic div instead of nav for <SidebarNavigationScreen />#51111
Use generic div instead of nav for <SidebarNavigationScreen />#51111
Conversation
|
Size Change: -4 B (0%) Total Size: 1.4 MB
ℹ️ View Unchanged
|
|
Thanks for looking into this. The unlabeled
Removing the unlabeled Note: out of the scope of this PR: the region now contains a mix of navigational and editing tools. I'm not sure this kind of mixed content is ideal in the first place. |
As for this, the entire area is always wrapped in a |
fad6eb3 to
32e7350
Compare
|
Flaky tests detected in 32e7350. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/5187564929
|

Closes #48652
What?
The
<SidebarNavigationScreen />of the editor used a<nav>element to wrap the content passed to it, but since its creation that content area has expanded to contain non-navigation content.Why?
The entire area is wrapped in a Navigation region, so the
<nav>element is no longer necessary or relevant in a lot of its uses.How?
Switch the
<nav>to a generic<div>.Testing Instructions
<nav>element in the sidebar markupScreenshots or screencast
Before:

After:
Same, but with a
<div>instead of a<nav>