InnerBlocks selection and display issues


We have experienced multiple issues with InnerBlocks, here is a quick summary:

  1. Using Shift+Select in the Navigator on blocks within a Component’s InnerBlocks causes the Component to fold up
  2. Editor bar displays multiple buttons when selecting nested components with InnerBlocks
  3. When nesting components with InnerBlocks, the blocks inside display cached old content after editing and switching focus

Step-by-step reproduction instructions:

Pleas see screenshot and screen recordings.

Screenshots, screen recording, code snippet

Editor bar has random button duplication:

Unable to Shift+Select blocks within InnerBlocks:

Cached content is shown when switching focus after editing blocks within InnerBlocks:

Environment info

  • WordPress version: 6.4.3
  • Cwicly Plugin version:

Hello @StrangeTech,

Thanks for this report.

Can you let me know if has addressed the issues you were experiencing here?

Thanks in advance.


Here is the current status as of

Regardless of modify mode or whether the target blocks are inside of an InnerBlocks, shift-select always immediately folds the component making it currently unusable within components.

This appears to be fully resolved.

This issue is still occurring with identical behaviour.

In addition, when testing these, I also found the following two issues:

  1. When copying a WP block (e.g. List block) from within an InnerBlocks in the navigator, you are not able to paste it using Cmd/Ctrl+V, only dragging it out works. This may be specific to blocks that hold other blocks, or may be specific to non-Cwicly blocks, we haven’t had time to fully test.

  2. When dragging a block out of an InnerBlocks onto the root level of a page, after it is dropped, any folded Div blocks on the same level automatically unfold. (We have enabled “Expand on Click” and “Expand all by default” in the navigator settings, we haven’t tested without these).
    Screenshot 2024-03-24 at 22.05.26

@Louis, just letting you know that this is still an issue with version

Hi @Louis, just making sure you have seen these messages. As they are client-facing and significantly affect usability for our clients.