Fullscreen Elm App in 0.19 (childNode issue) Reopened

For some additional context:

  • I think adding things at the end of the <body> should be fine as is.
  • I think it is possible to add some logic in virtual-dom to make it safe to add things at the beginning of <body> as well. Not 100% certain, but there is hope.

So if the extensions are all in these two categories, we may be able to just have things work out.

If the extensions are adding things in the middle of stuff, I’m not sure why they’d be doing it in the <body> any more than they’d be doing it in a random <div> somewhere.

So the point of gathering information is that we can figure out if there is a path that just sorts everything out without relying on a “this is not recommended” in the dev console.


If you want to help with this, just do it. Don’t wait for others to do it. Don’t wait for someone to start a “collab” where someone else does it. Just start installing common extensions and see if you can make things mess up with a Browser.application program that changes the number of root nodes on some timer or something.

If you do this, start a new thread where you share the test program and the list of extensions you tried. If multiple people do this, great, we have independent exploration and verification. Much stronger result.

9 Likes