Issue #2681💬 AnsweredOpened March 24, 2020by wemod1232 reactions

Destroy() method didn't fully remove events

Quick answerby emilsedgh1

I agree that this needs to be reopened and fixed within the destroy function itself.

Read full answer below ↓

Question

version: latest: v-0.16.3. important: update from v-0.15.9 to v-0.16.3 while keep everything same, the error will show in console: This error show there is a errro in function getFrameOffset, near position: e.ownerDocument.defaultView.frameElement: Refer to This Code Line Checking the error stack will track to This Code Line Expected: no error reported. Impact: I do not get specific negitive impact, only show the error. Reproduce: I integrate with Vue usage + webpack, hard to really reproduce, to debug this probaly check:simply add check chain to avoid TypeError:if this frameElement is requir...

Answers (3)

emilsedghJanuary 6, 2022

I agree that this needs to be reopened and fixed within the destroy function itself.

emilsedghJanuary 31, 2022

Thank you @artf ! 🙏

artfApril 3, 2020

Thanks for the report @wemod123 Are you able to create a reproducible live demo of the issue?

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

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.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.