Block inspector behaves erratically when using multiple editors

[vonloxx]

When using multiple editors, the block inspector component behaves erratically:

[johngodley]

You will need to design your system so this cross over is avoided.

[vonloxx]

ouch 😓 But it happens because the toggle actions uses the same interface store, maybe?

[johngodley]

Undoubtedly it is because of shared state. However, it is difficult to fully separate this as Gutenberg is just not designed for that kind of thing. Attempts have been made and some of these used to work well, but changes to Gutenberg along the way have meant that some things do bleed through. Is your example above a real thing or just theoretical?

[vonloxx]

Yep, I understand that. The examples above are taken from this repository storybook (Multiple editors) with inspector enabled.
Anyway, I'll try to come up with something to overcome, at least this issue.

[johngodley]

Ah ok, yes. It's a moving target so things will change. Hopefully full isolation can be brought back, but currently it's tricky.

[hawkidoki]

Hello!

I can report the same issue when using multiple instances of the Isolated Block Editor on the same page (within WordPress).

Did you find any workaround @vonloxx?

Thanks!

[vonloxx]

@hawkidoki Actually I ended using the block editor component (wrapped on my own components) since a lot of work was done so the block editor can work in a more "isolated" way. More info at WordPress/gutenberg#53874