Issue #6705Opened February 13, 2026by saeedhbi1 reactions

BUG: TypeError: Cannot read properties of undefined (reading 'toLowerCase') in keyboard handler

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

All browsers (Chrome, Safari, Firefox, Edge)

Reproducible demo link

https://jsfiddle.net/saeedhbi/tdsLa6qe/

Describe the bug

How to reproduce the bug?

  1. Create a basic GrapeJS editor (version 0.22.11 or 0.22.14)
  2. Add an input field component to the canvas
  3. Focus the input field
  4. Dispatch a KeyboardEvent where event.key is undefined for IME composition events (mostly in Chinese/Japanese/Korean keyboards)
  5. Observe TypeError: Cannot read properties of undefined (reading 'toLowerCase') in console

What is the expected behavior? The keyboard handler should gracefully handle cases where event.key is undefined and either:

  1. Skip processing for undefined keys, or
  2. Use a default/fallback value, or
  3. Check for event.key validity before calling .toLowerCase()

No error should be thrown, and keyboard functionality should continue working normally.

What is the current behavior? GrapeJS throws a TypeError when keyboard events originate from input fields and the event.key property is undefined. The internal keyboard handler calls event.key.toLowerCase() without null/undefined checks, causing the application to crash.

Error message:

TypeError: Cannot read properties of undefined (reading 'toLowerCase')

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

saeedhbiFebruary 18, 20261 reactions

Hi @artf, After digging deeper into the full stack trace, I found that the error is not in GrapesJS. The event.key.toLowerCase() call is coming from our own application code — a global window.addEventListener("keydown", ...) handler that we have elsewhere in our codebase, which runs alongside GrapesJS. Since our webpack build bundles multiple modules into the same chunk (dist/1348), The Sentry frame was misleading, and we incorrectly attributed the source to GrapesJS.

GrapesJS's own keyboard handling uses event.keyCode and is not involved in this error. This is entirely on our side, and we have a fix in place.

Regarding the jsfiddle, it was a genuine attempt to isolate the issue, not AI-generated. It simply wasn't set up correctly to reproduce the actual scenario. Closing this from our side, and apologies for the noise.

artfFebruary 18, 20260 reactions

Hey @saeedhbi, where exactly do you see event.key.toLowerCase() in our code? Are you sure is not coming from your side? Unfortunately, the jsfiddle is not helpful, seems too much AI slopped 😅, it's not even loading the editor.

Maybe you can share the full stack trace to see where exactly this happening?

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...

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.