Issue #5683Opened February 15, 2024by JonathanRiche0 reactions

BUG: Commands.runCommand not working for built in command

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

chrom v121

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug? 1.Go the the graepesjs.com/demo page open up the console and use the global editor object run the editor.runCommand( 'sw-visibility') method - built in grid lines And the command does not run even though its been set on the panel, I've had this setup in my project and recently upgraded from 0.20.3 to the latest v0.21.8 and noticed the editor.runCommand no longer works even when trying editor.runCommand( 'sw-visibility',{force:true}) no luck

What is the expected behavior? The command toggles the sw-visiibility command like the panel/button similar to the grapejs demo

What is the current behavior? toggle does not work programmatically anymore

If is necessary to execute some code in order to reproduce the bug, paste it here below:

editor.runCommand( 'sw-visibility')

Code of Conduct

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

Answers (1)

JonathanRicheFebruary 18, 20240 reactions

needed to run visualEditor.stopCommand('sw-visibility') first not sure if this is new runCommand used to toggle before with having to run stop

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.