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
Click the "Show"-button and then the "Hide 'modal'"-button.
This will trigger the error in the console and the onClick event won't be triggered.
Details
It only occurs in IE11, in Firefox and Chrome it works fine.
It only happens if the mapped view function has text "" at the first render (i.e. setting mapped = True in the init function in the example won't trigger the error).
Motivation
The reason we run into this problem is that we have want to conditionally render modals and we want to render these as high up in the DOM as possible to avoid stacking context problems. So do do this we have two view functions, one which renders whatever content is on the page and one for the modal which is conditionally rendered.
Workaround
The problem is very easy to work around, just return a div [] [] instead of text "", which is what we have done for now.
The text was updated successfully, but these errors were encountered:
Using
Html.map
for aview
that conditionally renderstext ""
or some content with event listeners crashes in IE11 with the error below.This is not one of the problems mentioned in #105 I think, although it might be related to #101.
SSCE
I've created an example project. To reproduce:
elm make src/Main.elm
;index.html
in IE11;This will trigger the error in the console and the
onClick
event won't be triggered.Details
text ""
at the first render (i.e. settingmapped = True
in theinit
function in the example won't trigger the error).Motivation
The reason we run into this problem is that we have want to conditionally render modals and we want to render these as high up in the DOM as possible to avoid stacking context problems. So do do this we have two view functions, one which renders whatever content is on the page and one for the modal which is conditionally rendered.
Workaround
The problem is very easy to work around, just return a
div [] []
instead oftext ""
, which is what we have done for now.The text was updated successfully, but these errors were encountered: