Adding blocks to Toggle only works for first Toggle

[MrDigii]

Description

If I add a Toggle block I can add multiple following blocks to the toggle as desired. If I add another Toggle block I only can add on block to it. All others are not recognized as a part of the Toggle block.

Environment

• Editor.js version: 2.28.0

• Plugins you use with their versions:

  • @editorjs/nested-list: 1.3.0
  • @editorjs/header: 2.7.0

• Device, Browser, OS: MacBook Pro M2, Chrome, Mac OS

Current behavior

If I add a Toggle block I can add multiple following blocks to the toggle as desired. If I add another Toggle block I only can add on block to it. All others are not recognized as a part of the Toggle block.

Expected behavior

No matter how many toggles are used, blocks can always be assigned to them.

Additional context

editorjs-toggle-block version 0.3.14

[MarioRodriguezS]

@MrDigii Thanks a lot for reporting the issue. We have been trying to reproduce the issue but with no success, Could you please provide more context or share a code sandbox with the error?

When I try to add several toggle blocks with the given dependencies versions:

[MrDigii]

@MarioRodriguezS Thank you for your fast response and effort.

I made a simple CodeSandbox to demonstrate the setup:
CodeSandbox

To show the problem I also made a GIF:

Thank's for your help :)

[balex25]

You have to press the 'Tab' button on blocks that want to move inside a toggle container.

[MrDigii]

You have to press the 'Tab' button on blocks that want to move inside a toggle container.

I my tests the 'Tab' button functionality is not reliable. Sometimes the block automatically belongs to the toggle sometimes not. Also the different block types can interfere because they also use the same keybinding to display their own settings.

So it's not very intuitive to use in my opinion. But maybe I missed something?

[miguelnietoa]

@MrDigii, thank you for reporting this. As you showed, currently, the toggle block plugin encounters limitations in handling List support effectively. We'll keep you informed of any developments on this matter.

[miguelnietoa]

@MrDigii @balex25, we're excited to announce the release of version 0.3.16, addressing the reported issue. Kindly review it and confirm that the fix resolves the issue for you. Thanks!

[MrDigii]

@MrDigii @balex25, we're excited to announce the release of version 0.3.16, addressing the reported issue. Kindly review it and confirm that the fix resolves the issue for you. Thanks!

I tested it in my application and it looks good now. Thanks for your effort @miguelnietoa and team :)