GrapesJS Issues

artf

Please follow the bug issue template properlyIf you don't indicate a reproducible demo with relative steps to reproduce the bug, the issue might be CLOSED.

GJS Helper

The issue description "multiple pages in importing css is not accessing" and "importing css is not working" is quite vague, but it points to a common misunderstanding of how GrapesJS handles CSS scoping and external stylesheet imports, esp...

mapsmarketing

One annoying thing is that the editor is prepending the below default styles which when saving the styles has numerous duplicates of it: Edit: Looking at the docs I finally managed to find protectedCss and when set to empty stops the style...

artf

Hi @mapsmarketing currently GrapesJS is not able to properly import HTML documents as string, so the parser skips elements like html, head, body and returns only what is parsed inside the body, one workaround you could do right now is to p...

mapsmarketing

Hi @artf , I've found a way to get the body attributes along with the styles saving correctly via the following method: I noticed that your Page.toJSON outputs everything of the specified page. However, it doesn't seem to output the styles...

antoinematyja

Hi, I encountered the same issue using Vue 3 and using a vue ref to store the editor. Not sure if this is a good idea though. A code reproduction would be something like: Fix: don't use a ref 😅

artf

Are you able to provide a reproducible demo? Tried your example and I don't see any freeze....

boardmain

tried with the latest version 21.7 i try to put it online, but i just pasted html from a custom command, the source is pasted, but after it, the editor freeze ( i need to close the page ) for example ~~~ btnImp.onclick = () => { editor.run...

artf

@ChiragS-Prajapati you have to use draggable/droppable component properties to control where components could be dragged and what components can be dropped inside.

GJS Helper

The issue you're encountering, where one section block can be dropped inside another, is a common behavior in GrapesJS by default. GrapesJS treats HTML elements like <div> and <section> as containers, allowing other components to be nested...

artf

The issue is caused by the use of jsInHtml: false and how the internal JS generator is handled. I'll try to fix it for the next release.

GJS Helper

The issue you've described is a known behavior in GrapesJS related to how component IDs are generated and optimized during HTML serialization. When a custom component has a script() function but no explicit styles applied to it, GrapesJS m...

GJS Helper

The issue you're encountering, where TailwindCSS classes like md:w-1/2 are transformed into md:w-1-2 when loaded into GrapesJS, stems from GrapesJS's internal class management and parsing logic. Root Cause GrapesJS, by default, processes a...

artf

Good catch @javadsamiee will be fixed in the next release

GJS Helper

The issue you've encountered is a known behavior in GrapesJS when initializing multiple pages with components that share the same initial IDs and corresponding inline styles. GrapesJS correctly identifies and renames component IDs to ensur...

bgrand-ch

@artf ❤️

GJS Helper

The component:styleUpdate event in GrapesJS is an editor-level event that is primarily triggered by the GrapesJS Style Manager or other internal editor mechanisms when a component's style is modified through the UI. When you directly call...

joukhar

yeah src folder is missing

artf

Same issue as https://github.com/GrapesJS/grapesjs/issues/5392

GJS Helper

Hello! You've correctly identified a change in how GrapesJS packages its styles starting from version 0.21.x. The main.scss file, along with the entire src/styles/scss directory, is indeed no longer included in the nodemodules/grapesjs fol...

GJS Helper

The issue you've encountered with duplicate CSS rules, specifically flex-wrap:wrap; for the .row class within the @media (max-width: 768px) block, is a known behavior that can occur in GrapesJS under certain conditions, often related to ho...