[Question] Should a class deselected on one component be deselected on other components?
Question
I'm not sure if this is a bug, or if I'm just misunderstanding usage.
Click component1 -> add class1 --> click the checkmark to deselect class1 on component1. Click component2 -> add class1
class1 will already be deselected. If you click the checkmark, then click component1, the checkmark for class1 is now selected on component1 as well.
I'm not sure I understand what the checkmark is expected to do. Should it be enabling/disabling the class for all components?
Answers (1)
No, it's not for disabling classes on components (in that case you have to remove it) but for changing the selector in Style Manager, so you can change what you need to style
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5990
BUG: When you delete a component, duplicate classes between components will be deleted.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 126.0.6478.127(Windows) Reproducibl...
Issue #868
[BUG]: "component:add" event triggers when components are moved
Taken from https://github.com/artf/grapesjs/wiki/API-Editorcomponent:add - Triggered when a new component is added to the editor, the model...
Issue #4247
BUG: Components disappearing/not being rendered at cloning, moving or adding
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chromium v96 Reproducible demo link https:...
Issue #3615
BUG: text in text component cannot update , cannot get final result from toHTML
it is text component, if select body, the text will correct save/apply/store in component toHTML method, if just updating text, but not lea...
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.