# Analysis of Elm core issues and patches

**URL:** <https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941>\
**Category:** Show and Tell\
**Created:** [November 26, 2021, 5:34pm UTC](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941 "2021-11-26T17:34:14Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![francescortiz](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/francescortiz/32/1721_2.png) [@francescortiz](https://discourse.elm-lang.org/u/francescortiz)\
**Post date:** [December 16, 2021, 1:37pm UTC](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941/21 "2021-12-16T13:37:20Z")

</div>

> [@rupert](#):
>
> the extra div approach screws up printer layouts apparently

I don’t know if I misunderstood the problem, but, if I did get it well, it seems to me that making Elm Apps crash for the sake of not having an additional `div >` in the print CSS seems to be overkill.

---

<div class="post-metadata">

**Author:** ![rupert](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/rupert/32/1775_2.png) [@rupert](https://discourse.elm-lang.org/u/rupert)\
**Post date:** [December 16, 2021, 2:43pm UTC](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941/22 "2021-12-16T14:43:06Z")

</div>

> [@francescortiz](#):
>
> I don’t know if I misunderstood the problem, but, if I did get it well, it seems to me that making Elm Apps crash for the sake of not having an additional `div >` in the print CSS seems to be overkill.

I kind of got the impression that the extra \<div\> approach is not enough to solve it. There are some plugins that still break that?

---

<div class="post-metadata">

**Author:** ![lydell](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lydell/32/178_2.png) [@lydell](https://discourse.elm-lang.org/u/lydell)\
**Post date:** [December 16, 2021, 5:32pm UTC](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941/23 "2021-12-16T17:32:10Z")

</div>

> [@rupert](#):
>
> There are some plugins that still break that?

Yes, Grammarly: [Grammarly also adds nodes deeply inside your HTML · Issue #12 · jinjor/elm-break-dom · GitHub](https://github.com/jinjor/elm-break-dom/issues/12)

(It’s been a while since I posted that issue and I haven’t re-checked since then, so there’s a chance Grammarly doesn’t do that anymore. But I’m sure there are other browser extensions that can insert a piece of UI deeper into the DOM.)

Also, Google Translate replaces text nodes with `<font>` tags (I believe to keep track of which pieces of text have been translated).

The approach I took in [GitHub - lydell/elm-safe-virtual-dom](https://github.com/lydell/elm-safe-virtual-dom) (unfinished) is letting you provide a JavaScript function that decides what to do with elements in Elm-controlled parts of the DOM that aren’t created by Elm (keep or delete).

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [December 26, 2021, 5:32pm UTC](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941/24 "2021-12-26T17:32:47Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.elm-lang.org/t/analysis-of-elm-core-issues-and-patches/7941.md?page=1)