You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elm fails to construct HTML <template> elements, probably because you're supposed to call appendChild and such on the element's content property instead of the element itself.
Example:
importHtmlexposing (..)
view =
node "template"[][
p [][ text "Test"]]
This will result in a <template> element with an empty #document-fragment in Firefox (109.0.1). In Chrome (110.0.5481.100) the p gets added outside of the #document-fragment, which isn't right either.
The text was updated successfully, but these errors were encountered:
cdfa
pushed a commit
to cdfa/zotonic
that referenced
this issue
Feb 27, 2023
…ly more general
This allows strict frontend frameworks like Elm to replace the `<script>` with some other element and still have it work.
Ideally, we would use a `<template>` instead of a `<script>`, but that also causes problems in Elm at the moment: elm/virtual-dom#185
…ly more general (#3308)
This allows strict frontend frameworks like Elm to replace the `<script>` with some other element and still have it work.
Ideally, we would use a `<template>` instead of a `<script>`, but that also causes problems in Elm at the moment: elm/virtual-dom#185
Co-authored-by: Colin de Roos <[email protected]>
Elm fails to construct HTML
<template>
elements, probably because you're supposed to callappendChild
and such on the element'scontent
property instead of the element itself.Example:
This will result in a
<template>
element with an empty#document-fragment
in Firefox (109.0.1). In Chrome (110.0.5481.100) thep
gets added outside of the#document-fragment
, which isn't right either.The text was updated successfully, but these errors were encountered: