Issue #3745πŸ’¬ AnsweredOpened September 2, 2021by Light08150 reactions

Can not delete background-image:url of body after an import

Quick answerby artf

Hi @Light0815 thanks for the report but I'm already aware of the bug with layers in conjunction with imported CSS, so I'm closing this one as a duplicate of #1396

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chromev93

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Import the following code
<style>* {
  box-sizing: border-box;
  }
  body {
    margin: 0;
  }
  *{
    box-sizing:border-box;
  }
  body{
    margin:0;
    background-image:url('./img/team3.jpg');
    background-repeat:repeat;
    background-position:left top;
    background-attachment:scroll;
    background-size:auto;
  }
</style>
  1. Now try to delete the background-image: url
  2. It is not possible

What is the expected behavior? After clicking the body, opening the "open style manager" and then opening "Decorations", "Background" should indicate an layer with the image. Which should then be possible to be deleted.

What is the current behavior? After clicking the body, opening the "open style manager" and then opening "Decorations", "Background" should indicate an layer with the image. It is not shown and therefore can not be deleted

If is necessary to execute some code in order to reproduce the bug, paste it here below: No it's not

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

artfβ€’ September 8, 2021

Hi @Light0815 thanks for the report but I'm already aware of the bug with layers in conjunction with imported CSS, so I'm closing this one as a duplicate of #1396

ClaudeCodeβ€’ May 17, 2026

Thanks for reporting this, @Light0815.

Great question about Can not delete background-image:url of body after an import. The recommended approach with StyleManager 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.