AsDocument not working as expected
Thank you, but that's not really the point. I'm fully able to make a workaround, but that does not fix the bug. The bug is that an export via getProjectData() followed by an import via loadProjectData() should result in the same state. Furthermore the hack you propose actually writes directly to the canvas meaning tha...
Read full answer below ↓Question
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 128 Reproducible demo link https://jsfiddle.net/sammousa/bxgsdc12/11/ Describe the bug How to reproduce the bug?Load an HTML string with a non empty <head>, using the option {asDocument: true}.Export the data via editor.getProjectData(), see that it contains the <head> contentLoad the exported data from 2 via editor.loadProjectData()Export the data via editor.getProjectData(), see that it does NOT the <head> content What is the expected behavior? I'd expect that this should always hold, may...
Answers (4)
Thank you, but that's not really the point. I'm fully able to make a workaround, but that does not fix the bug. The bug is that an export via getProjectData() followed by an import via loadProjectData() should result in the same state. Furthermore the hack you propose actually writes directly to th...
The bug is that an export via getProjectData() followed by an import via loadProjectData() should result in the same state.
Yeah definitely not expected, we'll look into it.
Appreciate the easily reproducible steps on the demo 👍
Thanks @SamMousa detailed bug reports are always welcome. If a direction is requested, we're happy to guide you 🙇♂️
The issue you've encountered is a known behavior (or a bug, depending on interpretation) in GrapesJS where the <head> content, initially loaded with editor.setComponents(html, { asDocument: true }), is not correctly re-applied or preserved when using editor.loadProjectData() to restore the project...
Related Questions and Answers
Continue research with similar issue discussions.
Issue #4967
New storage doesn't work
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfi...
Issue #4148
0.18.2 / 0.18.3 removes all on... HTML attributes when block is drag-dropped in the builder
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v99Reproducible demo link https://jsf...
Issue #5993
Empty panels are showing
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Opera 109 Reproducible demo link https://j...
Issue #5689
<> is introduced at the beginning editor.getHtml()
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 121.0.6167.185 (Official Buil...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.
Browse free plugins →Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.
Browse premium plugins →Related tutorials
In-depth guides on the same topic.
Tutorial
UnStudio for GrapesJS: 4 Plugins to Build Better Visual Editors
Meet UnStudio, a new GrapesJS plugin studio with four tools, safer and better editor: Command Palette, Responsive Pack, Autosave & Restore, and Autofill
Tutorial
Messaging on gjs.market: talk to a studio before you buy, not after
We've launched private messaging between buyers and studios. One thread per buyer–studio pair, the whole history in one place.
Tutorial
GrapesJS DevTools: A Developer Panel Inside Your Editor
If you've ever debugged GrapesJS with console.log(editor.getSelected()) and a dozen throwaway event listeners — this post is for you.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.