BUG: Custom block categories can't be named same as prototype object method names or it breaks Grapes

Question

GrapesJS version

I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome

Reproducible demo link

Version 118.0.5993.88 (Official Build) (arm64)

Describe the bug

How to reproduce the bug? Video demo part 1:

https://github.com/GrapesJS/grapesjs/assets/8781182/bfbbf6ea-7780-417e-880b-61992897c740

Part 2:

https://github.com/GrapesJS/grapesjs/assets/8781182/c61fa3b5-c62a-459d-bdf2-d8dc106e310b

Part 3:

https://github.com/GrapesJS/grapesjs/assets/8781182/b8540f2d-f52b-42ae-aaa5-87d6f9fb395c

What is the expected behavior? Sorry for the 3-part video, it was due to file size restrictions. The expected behavior is i should be able to name my custom block categories anything i want to, such as "constructor", without it breaking grapes.

What is the current behavior? Currently if you pick any built-in javascript object prototype method name (like "constructor"), then it breaks Grapes JS.

If is necessary to execute some code in order to reproduce the bug, paste it here below: https://jsfiddle.net/gratiafide/k04azsd9/8/

Code of Conduct

I agree to follow this project's Code of Conduct

BUG: Custom block categories can't be named same as prototype object method names or it breaks Grapes

Question

GrapesJS version

What browser are you using?

Reproducible demo link

Describe the bug

Code of Conduct

Answers (1)

Related Questions and Answers

BUG: When drag and drop block into editor in Chrome, not able to drag and drop block

BUG: paste command does not respect draggable/droppable properties

BUG: Component model and view inits every time it's dragged over every component present in Canvas on which it can be dropped into

BUG: Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?

Paid Plugins That Match This Issue

Browse Plugin Categories