Do not try to disable Grammarly in Slate (#4650)

* Do not try to disable Grammarly in Slate As the `data-gramm` attribute is no longer working actually. See #4124 The Grammarly extension is not causing the DOM issues anymore, as they have reworked their highlighting logic: https://www.grammarly.com/blog/engineering/making-grammarly-feel-native-on-every-website/ * Add changeset
ianstormtaylor · Nov 9, 2021 · b664313 · b664313
1 parent 9874ed7
commit b664313
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 4 deletions.
diff --git a/.changeset/wet-lobsters-travel.md b/.changeset/wet-lobsters-travel.md
@@ -0,0 +1,5 @@
+---
+'slate-react': patch
+---
+
+Do not disable Grammarly extension in Slate editors
diff --git a/packages/slate-react/src/components/editable.tsx b/packages/slate-react/src/components/editable.tsx
@@ -567,10 +567,6 @@ export const Editable = (props: EditableProps) => {
     <ReadOnlyContext.Provider value={readOnly}>
       <DecorateContext.Provider value={decorate}>
         <Component
-          // COMPAT: The Grammarly Chrome extension works by changing the DOM
-          // out from under `contenteditable` elements, which leads to weird
-          // behaviors so we have to disable it like editor. (2017/04/24)
-          data-gramm={false}
           role={readOnly ? undefined : 'textbox'}
           {...attributes}
           // COMPAT: Certain browsers don't support the `beforeinput` event, so we'd