BUG: DomComponents' Config Incorrect
Question
Version: 0.17.3
What is the expected behavior?
The documentation says that I can configure the wrapper element via the configuration:
Describe the bug detailed
I don't think that this configuration is used anywhere. A text search through the project for “wrapperName” returns only place I linked above itself. Searching for “wrapper” is not feasible unfortunately due to the high number of false positives.
I am able to configure the wrapper element after initialization using the object returned by editor.getWrapper().
Answers (1)
Yeah, actually the name, by default, is managed via i18n configuration.
From 0.17.* version even the wrapper option is not necessary anymore as now you should extend the wrapper component as all others (in previous versions the wrapper was initialized before plugins).
I'll remove them in the next release 👍
Related Questions and Answers
Continue research with similar issue discussions.
Issue #4735
BUG: resetId types mismatch
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? n/a Reproducible demo link n/a Describe th...
Issue #2894
[Question]: How Do I Hide / Disable Dropzone in AM Modal
Hello, I've been reviewing the documentation and this link, trying to find the right configuration setting to disable the dropzone in the A...
Issue #774
Mimic customRTE behavior when parsing content
Hi @artf, I'd like to replicate this behavior when calling editor.setComponents("<div>This is a text component. <span style='font-size: 20p...
Issue #3435
BUG: Scrollable onStart/onEnd/updateTarget not Overridable
Version: 0.17.3 Are you able to reproduce the bug from the demo?[ ] Yes[X] No What is the expected behavior? Being able to override onStart...
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.