Text element not able to be selected twice after extended with events
That actually was the problem. Thanks for replying. I'll be closing the issue.
Read full answer below βQuestion
Version: 0.17.25 Are you able to reproduce the bug from the demo?[ ] Yes[x] No What is the expected behavior? Update a existing component of type text by adding an event to his view. Describe the bug detailed The event is being added, but once I select another component I cannot go back to the first one. It can only be entered one time for edition. Are you able to attach screenshots, screencasts or a live demo?[x] Yes (attach)[ ] No first, i'm trying to extend the text type component to add an event to listen when something is typed. Even if I leave only a empty events property like events:{}...
Answers (4)
That actually was the problem. Thanks for replying. I'll be closing the issue.
+1 :D We are trying to solve this issue https://github.com/artf/grapesjs/issues/1136
Because it still happening when use a ckeditor.
The events are not automatically merged with the extended component so, you have to do it manually.
events: {
...domc.getType('text').view.prototype.events,
keypress: (e) => {...}
}
Thanks for reporting this, @gustavohleal. The issue with Text element not able to be selected twice after extended with events appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsi...
Related Questions and Answers
Continue research with similar issue discussions.
Issue #3681
Textable not working with extended text component
Version: 0.17.22 Are you able to reproduce the bug from the demo?[X] Yes[ ] No What is the expected behavior? Should be able to drop a text...
Issue #3454
RTE insert link does not update DOM
Version: "0.17.3" Are you able to reproduce the bug from the demo?[X] Yes[ ] No What is the expected behavior? After inserting link using d...
Issue #3131
Paste as plain text into Text component adds <font /> wrapper to pasted text
Version: 0.16.27 Are you able to reproduce the bug from the demo? [] Yes [X] No What is the expected behavior? Paste as plain text (text no...
Issue #3295
BUG (v0.16.41): Button component with draggable property is not working properly
Version: v0.16.41 Are you able to reproduce the bug from the demo? [ ] Yes [ ] No What is the expected behavior? When we have a button with...
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
Introducing GJS.Market Services: ship your GrapesJS editor without the integration risk
It's everything that usually eats weeks of engineering time, scoped and priced up front. No open-ended hourly surprises.
Tutorial
GrapesJS custom components guide (2026)
Define custom GrapesJS components with DomComponents.addType: detection with isComponent, a model with traits and defaults, and a view for canvas behavior.
Tutorial
Building an AI-Assisted Document Engine with Next.js, GrapesJS, and the AI SDK
Transform your static template editor into an intelligent, generative design workspace with Vercel AI SDK, AI Elements and Next.js.
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.