Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Grammarly Browser Extension Causes Loss of Focus When Using `textarea` Elements
See original GitHub issueThe Grammarly browser extension works by mutating the DOM. Whenever the user focuses a textarea element, the extension mutates it, which causes applications that expect no DOM mutations by anyone else to rerender (cf. https://github.com/facebook/draft-js/issues/616). The result is a loss of focus.
The Grammarly team knows about this issue (cf. https://www.grammarly.com/blog/engineering/making-grammarly-feel-native-on-every-website/) and is working on a solution. In the meantime, adding a data-gramm="false" attribute to textarea element prevents Grammarly from mutating it.
I’d suggest we add this attribute along with a comment to the textarea component.
Issue Analytics
- State:
- Created 10 months ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+1 on this feature I was advising an internal project when this problem came up on a team call. The result was that instead of using Camunda Modeler for business-IT collaboration, they returned to an Excel sheet.
Sure - I posted my issue in Slack with a video. Maybe I’m not used to seeing the autosave animation, but I found it distracting because it was firing all the time.
My expectation is that changing a field is an atomic action. I don’t expect it to be saved halfway through editing the field, especially because it can be invalid (e.g. FEEL expression).