Use the GitHub Issues EXCLUSIVELY for BUGS, FEATURE REQUESTS or QUESTIONS. Prefix the title of the issue with its context, eg. [Bug]: ....
Do a quick SEARCH first, to see if someone else didn't open the same issue
DON'T ASK to create examples/code for you, read DOCS and APIs first, then you can post what you have tried (we'd like to see your code) and what you're unable to achieve
All relative statements/questions have to be filled/answered, otherwise, the issue might be CLOSED
You're submitting a BUG
Are you using the latest release (older versions are NOT supported)?
If you're not sure, type grapesjs.version in console and press ENTER
Are you facing the bug with your local copy of GrapesJS or with the current demo?
If a local copy
Indicate all informations about your OS, browser and GrapesJS version.
Are you able to reproduce the bug from the demo?
What is the expected behavior?
What happens instead?
If you're able to reproduce the bug indicate all the necessary steps
Attach screenshots (using KAP/LICEcap), screencasts or live demo
WARNING
READ and FOLLOW next 5 steps, then REMOVE them before posting the issue
[Bug]: ....
You're submitting a BUG
grapesjs.version
in console and press ENTERYou're submitting a FEATURE REQUEST