You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks @kla-ko there is actually one logic that prevents selecting other components during component:remove events and I will fix it for the next release but what I'd suggest to you is to switch to another event.
The event component:remove is triggered for each removed component, which means it will be triggered for each nested one inside the one you decided to remove. You can use run:core:component-delete event which is triggered only once after the deletion command is completed and it should currently work without any fix.
GrapesJS version
What browser are you using?
Chrome Version 120.0.6099.225
Reproducible demo link
https://jsfiddle.net/wattnu/opmwfvjn/
Describe the bug
How to reproduce the bug?
editor.select(editor.getComponents().models[0]);
component:remove
handler is called.What is the expected behavior?
editor.select(editor.getComponents().models[0]);
shall work in the handlerWhat is the current behavior?
editor.select(editor.getComponents().models[0]);
shows no effect in the handlerCode of Conduct
The text was updated successfully, but these errors were encountered: