Conversation
… e2e test assertions can be made on blocks
…on over file names
| templateLock: 'all', | ||
| hasFixedToolbar: true, | ||
| } } | ||
| useSubRegistry={ false } |
There was a problem hiding this comment.
This is needed, as without this wp.data.select( 'core/block-editor' ).getBlocks() isn't usable globally—but it's needed in the test to assert which blocks are present.
There was a problem hiding this comment.
Just wanted to whine here. These true / false flags are so hard to pin down on meaning when reading code. Looking here it's not even mentioned.
|
Size Change: +9 B (0%) Total Size: 1.3 MB
ℹ️ View Unchanged
|
draganescu
left a comment
There was a problem hiding this comment.
Tested and the change makes the screen work as expected. The code and added test are 🆗
|
Hello @draganescu . Im getting this navigation screen error with the latest version of Gutenberg installed and the Block-Based Bosco theme and Attempt Recovery is not fixing it. Im attaching a screenshot of the error, can you please advise on the exact directory path for where I can update the code to fix this. |
|
@MarvelMoe Thanks for reaching out. The fix for this will be released in Gutenberg 9.8. Fixing manually is a little tricky as the code is compiled when shipped. |

Description
Fixes #28076.
The experimental navigation screen currently errors when trying to open it.
The
blockInformationisn't defined straight away, but that's not handled gracefully. I imagine this wasn't noticed because in other editors ListView only renders when the List View dropdown is opened, compared to the navigation screen where ListView is always rendered and visible.How has this been tested?
Added an e2e test.
Manual testing
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist: