What is your practice of handling runtime exceptions in Elm caused by DOM manipulations caused by browser extensions/plugins? We recently ran into this because of the Grammarly Chrome extension .

It definitely is. I’m now fishing for good practices around this.

+1 to this, @Birowsky . I don’t have an answer, but I ran into the same thing during a demo using an app I had written in Elm. While I didn’t figure out the problem, I observed that the Elm runtime seemed to recover without reloading the page when I disabled the plugin during the demo. Maybe it’s pos…

I read through the Chrome Plugins link above and realize now there’s a viable workaround I wish I had known about before. Oh well, please disregard my previous message.

How do you handle runtime exceptions caused by extensions? Case by case. There is no systemic approach because the very concept of virtual DOM is flawed. It can’t get over the unfortunate fact it’s not the only one to modify the DOM.

Another viewpoint is that the very concept of browser plugins is flawed. Browsers should show websites as they are meant to be shown and not modify them in any way. So don’t try to handle the runtime exceptions caused by extensions in any way - just inform users that they should not use browser plu…

Hold up. What is this viable workaround you speak of? Or are you referring to jinjor’s patch?

At work we render all our textareas using two helpers functions, so we added Html.Attributes.attribute "data-gramm_editor" "false" to both of them. That got rid of the majority of all virtual dom errors in our error tracking service.

@jinjor ’s workaround: data-gramm_editor=“false”.

At my last job we had trouble with some browser extensions trying to add their own html elements to the top of the <body></body> tag’s children. Which would lead to the Elm virtual dom finding a different element than it expects at certain positions in the dom. The solution we came to, that we lear…

How do you handle runtime exceptions caused by extensions?

Learn

ymtszw July 2, 2020, 2:39pm 2

Haven’t looked up recently but Runtime errors caused by Chrome extensions is a related issue.

Topic		Replies	Views
Runtime errors caused by Chrome extensions Request Feedback	18	5056	October 4, 2019
Fullscreen Elm App in 0.19 (childNode issue) Reopened Request Feedback	24	5866	February 23, 2019
JavaScript Exception: Cannot read property childNodes of undefined, with extension Dark Reader Learn	4	7161	December 16, 2018
Elm app not compatible with ChromeVox screen reader Request Feedback	6	1348	May 24, 2019
Published an NPM package to prevent browser extensions from crashing Elm apps Show and Tell	0	597	July 21, 2022

How do you handle runtime exceptions caused by extensions?

Related topics