OS version: 1903 (OS Build: 18326.295) Browser: Edge(Microsoft Edge 44.18362.267.0) User Experience: If tooltips are not accessible with keyboard inside editor, than keyboard user will not be able to understand the control purpose and will face difficulties while interacting with it. Steps to reproduce When user moves...
Hey @artf I get the error Cannot read property 'hasFocus' of null when i press 'a', 's', 'd' and 'w' from the keyboard on input text components in the canvas. Uncaught TypeError: Cannot read property 'hasFocus' of null at Object.hasFocus (grapes.min.js:12) at run (grapes.min.js:3) at Object.method (grapes.min.js:12) a...
MariusDK
It's about keymaps: d stands for core:component-delete a stands for core:component-exit s stands for core:component-next w stands for core:component-prev To solve the error i have to use:Remove all binded keymaps editor.keymaps.removeAll()...
Hello, I use Grapesjs in my reactJS application. I have a react component which is an instance of Grapesjs. So I can add this component in my application as many times as I want. Everytime I want to fire an event (delete a block) with my keyboard in the grapesjs Editor, it doesn't work. This is the error throwing: But...
artf
Can you provide a reproducible live demo of your case, please? ps. make sure to work with the latest version of grapesjs
no-response[bot]
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take ac...
lock[bot]
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
The demo looks great, but points to the need of a serious accessibility review. There is an open issue in the Drupal community looking at this, and we are working on a good pattern. The start though is having elements be focus-able for keyboard only users.
artf
Thanks Mike for pointing this out, I definitely add this to the Roadmap (#74)
ankx06
@artf just wanted to check about the timeline to add this feature. I see that you have moved it to backlog, so what is the plan to support focus on each component via keyboard.
mgifford
Ya, sorry.. Been a while since I posted this link in 2017.. Had kinda forgotten what the focus of GrapeJS is. But ya, as I said 5 days ago, accessibility "isn't something you can just 'turn on'."