Paste as plain text into Text component adds <font /> wrapper to pasted text

@artf do you know if this is this happening in the component or the RTE or somewhere else? Could you please point me in the right direction? Any help on this would be greatly appreciated. Thanks!

I can't reproduce it, but I see you're using a custom dm-text component, so that might be a reason?!

@artf I don't believe so. Here is the configuration of the dm-text component type

{
  extend: 'text',
  model: {
    defaults: {
      name: 'Text',
      traits: [],
      editable: true,
      droppable: false,
      textable: true,
      style: {
        padding: '10px',
        width: '100%',
        height: 'auto',
      },
      stylable: [
        'background-color',
        'page-break-inside',

        'color',
        'text-align',
        'font-size',
        'font-family',
        'font-weight',
        'line-height',

        'border-width',
        'border-color',
        'border-style',

        'padding',
        'padding-top',
        'padding-right',
        'padding-bottom',
        'padding-left',

        'border-top-left-radius',
        'border-top-right-radius',
        'border-bottom-right-radius',
        'border-bottom-left-radius',
      ],
    },
  },
};

Do you see anything here that might be causing it?

Thanks for reporting this, @Joshmamroud.

The issue with Paste as plain text into Text component adds <font /> wrapper to pasted text 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