You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I started using your plugin which was exactly what we were looking for. But my use case for grapesjs is quite specific, when I save the generated code I don't store css elements with selectors like body, *, etc..
I was wondering if there is a way to avoid removing these when deleting css in the editor, without removing the funcitonnality, I still want people to be able to write their own css and remove theirs. But I don't want them to remove the defaults.
(in red should not be removed)
The text was updated successfully, but these errors were encountered:
Hi, I started using your plugin which was exactly what we were looking for. But my use case for grapesjs is quite specific, when I save the generated code I don't store css elements with selectors like body, *, etc..
I was wondering if there is a way to avoid removing these when deleting css in the editor, without removing the funcitonnality, I still want people to be able to write their own css and remove theirs. But I don't want them to remove the defaults.
(in red should not be removed)
The text was updated successfully, but these errors were encountered: