Selector:remove event does not exist
Hi @Justin8303 selector:remove refers to the global container of selectors so it's only triggered when the selector is actually removed from the global collection and not from the component. When you remove the selector from the component, it still exists as it might also be used somewhere else. If you need to track c...
Read full answer below ↓Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
Chrome 101
Reproducible demo link
https://jsfiddle.net/sdrf72wx/1/
Describe the bug
How to reproduce the bug?
- execute the code below on the initialization of the editor
- add and remove a selector of a component
- Look at the console output
What is the expected behavior? If a component selector is removed, it should print the selector to the console.
What is the current behavior? There is no console message, if the selector is removed, so the "selector:remove" event is not firing. Also, the "selector" event only catches "selector:add" and "selector:update" but NOT "selector:remove" but in the event section of the Selector Manager they are available.
If it is necessary to execute some code in order to reproduce the bug, paste it here below:
editor.on("selector:remove", (data) => {
console.log(data)
})
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (2)
Hi @Justin8303 selector:remove refers to the global container of selectors so it's only triggered when the selector is actually removed from the global collection and not from the component. When you remove the selector from the component, it still exists as it might also be used somewhere else.
If you need to track component classes changes, I'd suggest using the component:update:classes event
Thanks for reporting this, @Justin8303.
Great question about selector:remove event does not exist. The recommended approach with Components is to use the event-driven API.
Start here:
- Check the GrapesJS documentation for your specific module
- Look for the
on()event listener method - 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.
Issue #5173
editor.Css.setRule API not working as expected, it is not updating the rule existing rule.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 112.0.5615.137 (Official Build) (a...
Issue #6458
sector.setName doesn't work
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfi...
Issue #5460
Loading `component` and `styles` from `pageManager`
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v117.0.5938.149Reproducible demo link...
Issue #5982
Component styles such as md:flex-row(tailwind) are removed
GrapesJS version[x] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 126.0.6478.127Reproducible demo link...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →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.
Tutorial
Find the Right GrapesJS Plugin in Seconds: Smarter Discovery Is Live
We're shipping a set of discovery upgrades. New label filters, a proper compatibility switch for GrapesJS vs Studio, one-click and a smarter sort bar.
Tutorial
GrapesJS vs Webflow vs Tilda: What to Choose for Your Business in 2026
Choosing the right website platform in 2026 is no longer just about building a site
Tutorial
GJS Market 2.0 - Donations, Tracking, Labels and Better Product Discovery
We’ve rolled out a new set of GrapesJS marketplace updates across GJS Market, focused on improving how creators distribute products
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.