BUG: Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?
Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
latest version of Chrome
Reproducible demo link
null
Describe the bug
How to reproduce the bug? <img width="1666" alt="image" src="https://github.com/GrapesJS/grapesjs/assets/114127651/c37e339a-e14f-486b-85fb-34c170b855dd">
What is the expected behavior?
What is the current behavior? I use rewrite ctrl + c and ctrl + v logic <img width="681" alt="image" src="https://github.com/GrapesJS/grapesjs/assets/114127651/c056010a-d680-439b-a381-0aa36fd7e2ac">
I have set up three parent components and use ctrl+c,ctrl+v to added some child components to them. After deleting these child components, their styles still remain.
If is necessary to execute some code in order to reproduce the bug, paste it here below:
// your code here
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (3)
Yes , you are right, I copying all matched styles ,so I can paste anywhere , even cross-browser paste, I find this to be extremely useful. When I delete a component, it does not remove the corresponding styles. This is a major issue, And when I copy and paste multiple times on the same website, it leads to a lot of redundant styles and easily causes style conflicts. so I can't simply expect those styles to be deleted. If possible, I would appreciate some suggestions.
If you're copying all matched styles it would also contain styles used by other elements so you can't simply expect those styles to be deleted.
it‘s still a problem
I don't see how this is a core bug. You're using your own copy/paste logic and it doesn't even seem correct, you should take care of the unique ids of each component/rule.
After deleting these child components, their styles still remain.
If you're copying all matched styles it would also contain styles used by other elements so you can't simply expect those styles to be deleted.
Please, if you're submitting a bug, ALWAYS provide a reproducible demo.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5346
BUG: Deleting a component without deleting its corresponding style
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo...
Issue #5105
BUG: Adding style o component by (prop, value), isn't work correct.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome@latest Reproducible demo link https...
Issue #4376
BUG: Unselected custom component will also listen to event 'styleable:change'
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome 100 Reproducible demo link https://...
Issue #3806
BUG: Target :null when adding video
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome new version Reproducible demo link...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.