0.18.3 text editing not triggering for link > text components

Yeah, I see the problem.

Double clicking text elements (span, i...) inside a switches focus to the parent a element instead of opening rte for the selected element

With the new logic implemented for the text components view, this is intentional. The idea was to prevent having nested RTEs by passing editing to the closest component with RTE.

Unfortunately, links have also their own logic applied during parsing in order to prevent RTE with links as blocks.

<a href="...">
 <img .../>
 <h3>Block title</h3>
 <p>Block description</p>
</a>

I'll try to fix it, unfortunately, some opinions are necessary by default here, but at least you should always be able to suppress them by extending components.

Thanks for reporting this, @lofcz.

Great question about 0.18.3 text editing not triggering for link > text components. The recommended approach with ProseMirror is to use the event-driven API.

Start here:

1. Check the GrapesJS documentation for your specific module
2. Look for the on() event listener method
3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

• Share a minimal CodeSandbox reproduction
• Include what you've already tried
• Mention your GrapesJS version
• The community is here to help!