The Navigation Block has an Inline Style Without Declarations. #62358
Labels
[Block] Navigation
Affects the Navigation Block
[Type] Bug
An existing feature does not function as intended
Description
The bug is an inline style attribute without declarations.
The Bug is in the Navigation Block. And the issue lies within the Overlay Menu. Furthermore, the bug appears with the Overlay Menu options:
• Mobile
• Always
The bug appears in the page's (rendered) HTML. The HTML with the empty style attribute is below.
<div class="wp-block-navigation__responsive-container" style="" id="modal-1" data-wp-class--has-modal-open="state.isMenuOpen" data-wp-class--is-menu-open="state.isMenuOpen" data-wp-watch="callbacks.initMenu" data-wp-on--keydown="actions.handleMenuKeydown" data-wp-on--focusout="actions.handleMenuFocusout" tabindex="-1">
Step-by-step reproduction instructions
You can see the following steps in the screen recording below.
Steps
Log Into WordPress and activate Theme Twenty Twenty-Four.
Edit The Navigation Block
Edit the Navigation Block via the Home Page.
• Home Page
• Edit site
• Edit Blog Home
• In the Header area, select the Navigation Block.
• Go to the Navigation Block Settings
Change The Overlay Menu Settings
The bug is in the Overlay Menu settings Mobile or Always.
• Overlay Menu = Always
• Save
• View Site
View The Bug In (Rendered) HTML
Open your browser Developer Tools and find the webpage's HTML DOM Tree.
The empty inline style attribute is in a div element containing the class wp-block-navigation__responsive-container. (See below.)
<div class="wp-block-navigation__responsive-container" style="" id="modal-1" data-wp-class--has-modal-open="state.isMenuOpen" data-wp-class--is-menu-open="state.isMenuOpen" data-wp-watch="callbacks.initMenu" data-wp-on--keydown="actions.handleMenuKeydown" data-wp-on--focusout="actions.handleMenuFocusout" tabindex="-1">
Screenshots, screen recording, code snippet
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: