GrapesJS Issues

artf

Hi @BenKhz that's happening because selector* events are related to the global Selectors container (when you remove a selector from the component, the Selector itself is still there as it could be used in other places), if you want to trac...

BenKhz

Ah! I was misunderstanding. Thank you for the clarification. Keep up the good work!

ClaudeCode

Thanks for reporting this, @BenKhz. The issue with Editor not subscribing to selector:remove appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications ov...

artf

Hi @rajevar I think you're looking for component:create event, as component:add works as expected (eg. might be used to track any new movement inside a specific component)

ClaudeCode

Thanks for reporting this, @rajevar. Great question about "component:add" event triggers when components are moved. The recommended approach with Canvas is to use the event-driven API. Start here: Check the GrapesJS documentation for your...

artf

The error here is using the arrow function, just replace it with clickOnElement() {

ClaudeCode

Thanks for reporting this, @fluke777. Great question about Event handler on view not bound to the component. The recommended approach with Canvas is to use the event-driven API. Start here: Check the GrapesJS documentation for your specifi...

pittleCheung

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 w...

pittleCheung

it‘s still a problem

artf

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...

artf

@joukhar npm install GrapesJS/grapesjs#dev is not enough, I didn't create the build in the dev branch yet, so if you want the fix locally you have to build it yourself first. Anyway, there is no need to create new issue even if the related...

ClaudeCode

Thanks for reporting this, @joukhar. The issue with textnode with content "null" is rendered as "null" not whitespace appears to be a race condition or state management timing problem. This typically happens when component lifecycle events...

artf

Hi @bgrand-ch unfortunately everything that involves the parser (HTML/CSS) requires the DOM related API to be available. For the CSS maybe you can try to use parser-postcss plugin, I'd expect it to work in the worker environment

bgrand-ch

Hi @artf, thanks a lot for your quick answer 😄 I will try this week.

bgrand-ch

@artf The Post CSS parser plugin works perfectly in a web worker! Thanks for your help.

artf

Probably in the first week of August

artf

Hi @joukhar is it happening with the latest version? I'm able to see nulls in the export code if I use your exact JSON example (that should be fixable), but I'm unable to generate those textnodes with nulls by using your HTML example, can...

joukhar

thanks for the replay, if you need demo so please give me some time until i make one , i will comment again when im finished it the problem happens only when u store it and load it, but when u drop the component for the first time nothing...

gxanshu

Hi there! 😊 I don't believe this is a bug with GrapesJS. I checked your reproduction link and tried adding a component to the canvas, and it worked perfectly fine for me without any issues. 👍

artf

You have to bypass Vue's Proxy observers https://github.com/GrapesJS/grapesjs/issues/4497#issuecomment-1213078160

ClaudeCode

Thanks for reporting this, @Zafermushtaha97. The issue with bug appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsiste...

artf

Thanks @rmadeiraneto for the report. Yeah, unfortunately that's an issue if you're mutating arrays/objects properties in that way and to avoid that you have 2 options:Avoid direct mutations (assign new references when you have to update th...

rmadeiraneto

@artf using defaults as a function works, thanks for quick response and for providing the alternative fix on this issue. About the first suggestion, I think it's not about people should mutate or not the object, because we're talking about...

ClaudeCode

Thanks for reporting this, @rmadeiraneto. Great suggestion about Changes in component's attributes being reproduced in all the instances instead of just one! While this specific feature isn't yet in the core API, there are several ways to...

artf

Thanks @acantepie please open the issue in the proper repo as this is not core related one

ClaudeCode

Thanks for reporting this, @acantepie. Great question about Toolbar of ckeditor components is not correctly refreshed. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation...