Conflicts with Grammarly

Hiya,

Unfortunately there’s no plans to make any changes in Gutenberg to accommodate various browser extensions (there’s just too many for us to reliably test with and guarantee will work).

The Grammarly devs are aware of the problem and are looking into it on their side of things.

You can see the entire discussion at https://github.com/WordPress/gutenberg/issues/1698

Thanks for the link. Well, that’s quite normal when two teams are aware and nobody cares. Besides the fact that WP Gutenberg transforms a content-centric editor into an ordinary page builder and the blogging experience into a page building experience, it also brings a lot of pain to authors and editors. They don’t even have an option to turn that page builder off! It’s way too disruptive approach.

Hiya Marius,

As someone who uses WP and benefits from all those who volunteer their time and effort, I appreciate your creation. So, thank you for your good efforts.

Since we do use WP for writing, I would urge Word Press developers to think about the advantages of a spell and grammatical check. It is central to the act of writing. And what is a blog? A tool for writing.

Grammarly helps keep writers from embarrassing ourselves online. What word processing app lacks grammar-check and spell-check these days?!? Seriously, name one (besides WP Gutenberg). Having zero grammatical review before publishing a blog post for all the world to see makes absolutely no sense to me. It flies in the face of logic.

Please think about UX.

As you prioritize development of WP, I urge WP developers to enable some kind of grammatical functionality. Grammarly should work in WP Gutenberg. Heck, it works in this interface as I type. It is a Chrome extension. Might there be a relatively easy fix that would enable it to work in WP? Given the critical importance of having that kind of functionality, has anyone looked into that?

At present, writers must copy/paste what they’ve written into an app where Grammarly does work such as Google docs or Gmail or Slack or Medium or Twitter or Facebook or LinkedIn.

Making more work for your users is generally not a good thing. (What would Steve Jobs say?) If you want writers to do their writing in WP Gutenberg, some might argue that it is wrong-headed to insist that we do it without a grammatical and spelling safety net.

(And, though I generally love advances in user interfaces, I have turned off WP Gutenberg. It made mincemeat out of the Divi builder experience.)

Thank you for your kind consideration.

• This reply was modified 5 years, 9 months ago by krista06880.

Hiya,

Just a heads up, this topic is many months old, and will be closed after this reply, as it’s another users topic. If you are experiencing further issues I would recommend creating your own topic so that we do not bother the previous topic participants.

The Grammarly browser extension is not something we can control, or account for. There are tens (hundreds) of thousands of extensions, we just can’t do that, we need to focus on our own editing tools.

As noted the Grammarly team are aware of the incompatibility, and were at the time working on fixing it on their end (this because it was also not compatible with major social media text fields, so it was a larger issue than just our editor, the ticket referenced earlier mentions facebook for example). If they are still working on it, or have abandoned support, I can’t say, that’s honestly something you will have to contact them about, it’s an extensions responsibilities to work with websites, not the other way around ??