A tag inside button is removed

This happens because of the button implementation in the forms plugin, which allows only textnodes as children.

If you remove the form plugin you'll be able to see the <a> element (if you prefer you can also extend the button component with your own logic).

so what is the code of "normal" implementation of the button? btw, may I know why do you make the button to behave like that on the forms plugin?

If I recall properly the main reason there was a problem with inline text editing with button elements, so that approach was the easiest way to fix a common issue. I guess the "normal" implementation would be to skip/overwrite the init method but you should think on how to properly handle the inline text editing.

Thanks for reporting this, @handhikadj.

Great question about a tag inside button is removed. The recommended approach with GrapesJS 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!