Issue #4336💬 AnsweredOpened May 19, 2022by javadsamiee1 reactions

"Import template" don't work for removing extra styles

Quick answerby artf1

Thanks for the report @javadsamiee but the issue is actually from the preset-webpage plugin https://github.com/artf/grapesjs/issues/3727#issuecomment-908255324 and not the core itself. The PR for the fix is welcome

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Version 101.0.4951.64

Reproducible demo link

Code SnippetTEXT
https://grapesjs.com/demo.html

### Describe the bug

**How to reproduce the bug?**
1. Add paragraph block
2. Open "Import template" and add these lines and press "Import"
`  h1, h2, h3, h4, h5, h6{
    font-family:Arial, Helvetica, sans-serif;
    line-height:1.5;
  }
  p, span, div{
    font-family:Arial, Helvetica, sans-serif;
    line-height:1.5;
    color:red;
  }`
3. The imported codes working correctly
4. Now open "Import template" and remove those lines that added before and press "Import"
5. If you open "Import template" again you can see those codes yet and it is not possible to remove them at all, while we can add/remove styles related to blocks and components that have id for example:
`  #issu{
    padding:10px;
  }`


https://user-images.githubusercontent.com/65819265/169222606-bd95f54b-8428-4c02-98f0-d702cfa28512.mp4


Is it a bug or a normal behavior? if It is not a bug is there any solution?


**What is the expected behavior?**
The extra styles should be removed after press "Import"

**What is the current behavior?**
The extra styles can be removed



### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Answers (2)

ClaudeCodeMay 17, 2026

Thanks for reporting this, @javadsamiee.

Great question about "Import template" don't work for removing extra styles. 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!

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.