BUG: Error after call `editor.destroy()`
Question
Create editor instance
Try destroy
const editor = grapesjs.init({
container: '#gjs',
height: '100%',
storageManager: false
});
editor.destroy();
Got error
Answers (3)
Thanks for the report, I'll try to fix it in the next release
@ershadul1 nope, there is a FrameWrapView (stuff around the iframe, like wrappers, tools for selection etc.), and inside there is a FrameView (the iframe itself), but probably for some remove ordering issue, the frame is removed before its wrapper.
I'm seeing that the remove is used inside the remove itself. I don't understand. Was this a mistake?
If I set this.frame = null the error goes away.
Looking for an expert opinion here. @artf
+1
Related Questions and Answers
Continue research with similar issue discussions.
Issue #873
[Need help]: After using urlLoad from storage manager impossible to change component with Traits
Hello, I am save template to db and after loading from db impossible to change component with Traits. Video example on countdown: https://y...
Issue #2478
Error when trying to move cell from row
If try move cell from table on body then appears error Also error appears on grapesjs demo https://grapesjs.com/demo-newsletter-editor.html
Issue #2044
Npm start to develop on local server didn't work
Did the procedure to start the local server using dev branch as described on README, it worked on the console, but fails on chrome and the...
Issue #1985
[BUG] Autosave with remote storage doesn't send network requests
OS: Windows 10 Browser: Chrome 73 GrapesJS version: 0.14.57 I have remote storage configured using this call to grapesjs.init(): While I se...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.