search

decaporg / decap-cms

A Git-based CMS for Static Site Generators
https://decapcms.org
MIT License
17.7k stars 3.03k forks source link

Markdown widget does not support content modification by Grammarly #4737

Open tonyketcham opened 3 years ago

tonyketcham commented 3 years ago

Describe the bug

Note: This could be an issue with Grammarly and not NetlifyCMS, but this is the only platform that I've experienced this issue with. It does not occur with any other markdown/ WYSIWYG/rich text editor I've used.

Text in the markdown widget is not updateable by Grammarly. Selecting the extension's suggested grammar fixes dismisses the error notification that the extension provides while not updating the content.

However, text input in other widgets works just fine with Grammarly.

Since a lot of writers and publishing editors often use Grammarly as part of their editorial workflow, this could be an annoyance or even accidentally introduce errors into content when the uncareful eye sees the error underline disappear after accepting the fixes proposed by Grammarly.

To Reproduce

  1. Have Grammarly installed
  2. Intentionally misspell something in a markdown block
  3. Choose the suggested fix
  4. Verify that the content doesn't update with the suggested fix

Expected behavior markdown widget content should be updatable by browser extensions.

Applicable Versions:

CMS configuration real world example of an affected config.yml

its-a-lisa commented 3 years ago

This happened to me too.

tonyketcham commented 3 years ago

Tested on Safari 14.0 and this issue did not occur

boehs commented 3 years ago

also have this issue

Browser is vivaldi

igorwojda commented 3 years ago

The same problem in Edge 88.0.705.74 (Official build) (64-bit)

boehs commented 3 years ago

Awesome, great to see this recognized finally, thanks @erezrokah !

igorradovanov commented 3 years ago

Any updates on this issue? This seems to occur on both the latest versions of Netlify CMS and Grammarly.

erezrokah commented 3 years ago

Hi @igorradovanov, the best way to move this forward is to submit a contribution for it.

ali4zimi commented 1 year ago

It happened to me also. Is it still under development?

martinjagodic commented 1 year ago

@ali4zimi the best way to move this forward is to submit a contribution for it.

ali4zimi commented 1 year ago

@martinjagodic I tried to set up local development but I couldn't figure it out. I use WSL, and already tested node versions 19, 18, and 16. Can you give a hint on this?

martinjagodic commented 6 months ago

Grammarly works for me until I add an editor component. Does anybody experience the same problem? Using Decap 3.0.12