Description

With the classname changes in #33918, the isNavigationChild attribute was added to the Page List block, so it can render with the navigation-specific classnames when necessary. But because the attribute is being updated inside a useEffect, it isn't present on first render of PageListEdit, resulting in Page List blocks not getting the right classnames when first added to the Navigation block.

This PR fixes the issue by updating isNavigationChild before the component first renders.

How has this been tested?

Create a few pages on your test site, and set a few of them to be children of another page.
Add a new navigation block to a post, and choose "Add all pages".
Add another navigation block, choose "Start empty", and then add a Page List block inside it.
Verify that in both cases, the Page List renders child pages correctly as submenus of their parents.

Screenshots

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

• [x ] My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR (please manually search all *.native.js files for terms that need renaming or removal).