0.18.3 text editing not triggering for link > text components
Yeah, I see the problem. Double clicking text elements (span, i...) inside a switches focus to the parent a element instead of opening rte for the selected element With the new logic implemented for the text components view, this is intentional. The idea was to prevent having nested RTEs by passing editing to the clos...
Read full answer below βQuestion
GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 99 Reproducible demo link https://codesandbox.io/s/distracted-archimedes-fhmnpg Describe the bug How to reproduce the bug?open the demodouble click "I am text" component. What is the current behavior? Double clicking text elements (span, i...) inside a switches focus to the parent a element instead of opening rte for the selected element. This works correctly in 0.18.2. From the template here https://codesandbox.io/s/1r0w2pk1vl minimal reproduction is to patch index.html from to Code of Con...
Answers (2)
Yeah, I see the problem. Double clicking text elements (span, i...) inside a switches focus to the parent a element instead of opening rte for the selected element With the new logic implemented for the text components view, this is intentional. The idea was to prevent having nested RTEs by passing...
Thanks for reporting this, @lofcz. Great question about 0.18.3 text editing not triggering for link > text components. The recommended approach with ProseMirror is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the on() event listener met...
Related Questions and Answers
Continue research with similar issue discussions.
Issue #4851
This.on('change:attributes:type', this.handleTypeChange) do not support array type
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 108.0.5359.125Reproducible demo link...
Issue #5263
Deleting a component without deleting its corresponding style, will adding new components later cause style conflicts?
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest version of Chrome Reproducible demo...
Issue #4601
Update() of custom types added to StyleManager is no more triggered when switching between some targets.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chromium 104 Reproducible demo link https:...
Issue #5487
Style Manager doesn't display multiple rules for the same class
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link https://jsf...
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.