Problem with copy and paste a node

I've tried locally but the node is placed correctly. Are you able to create a live demo, please?

Sorry, I did not elaborate on the scenario where this error occurred. The components that come with grapesjs do not produce this error, because they don‘t have spaces，carriage returns or tabs. I found this problem while customizing components. I have customized a lot of my own components, and some of them will have this situation. An example of the initialization of the custom component node that found this problem is as follows.

viewTemplate() {
    return '
      <form data-gjs-type="form-panel" class="form-panel">
      </form>
    '
  },
...
 onViewInit() {
    const comps = this.model.get('components');
    if (!comps.length) {
      comps.reset();
      comps.add('
        <div class="form-panel-group" data-gjs-type="form-panel-group"><label class="label">多/单选：</label><div data-gjs-type="select-comp" class="select-comp"></div></div>
        <div class="form-panel-group" data-gjs-type="form-panel-group"><label class="label">多选选择：</label><div data-gjs-type="mdc-checkbox-group" class="mdc-checkbox-group"></div></div>
       </div>
      ')
    }
    ...
  }

If you want to reproduce this problem in the grapesjs default component, you can enter a space between nodes through the “Editor as HTML” of the f12 Elements . as follows.

@artf I accidentally closed the issue.

Thanks for reporting this, @nanaya1.

The issue with Problem with copy and paste a node appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

1. Add a setTimeout wrapper to ensure the DOM has settled:

setTimeout(() => {
  // your operation here
}, 0);

2. Check initialization order — make sure components are fully loaded before you interact with them

3. Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

• Test with the latest GrapesJS version if you haven't
• Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
• Include GrapesJS version, browser, and console errors in your report