Exception in JS port handler causes Signal to stop updating

[robertjlooby]

If a Signal is sent out a port, and the handler errors on the JS side, then the value of the Signal stops updating on the Elm side after the first update.

There is a small example of it here. The displayed time should update once a second to the current time. You'll see it update the display once (which throws the first error) and after that it just errors with the "notify message has been called synchronously" message and the Signal stops updating on the Elm side. There is a related issue here but it seems mostly concerned with providing a more accurate error message.

As a more practical example, the todomvc app will not work on Safari in a private window because any access to localstorage throws an error.

---

[evancz]

Not sure if this is still true, but there at least are not signals anymore. It may persist in 0.17, but I think that'd need a different SSCCE.

[evancz]

Not sure if this is still true, but there at least are not signals anymore. It may persist in 0.17, but I think that'd need a different SSCCE.

[evancz]

Also sorry for the slow response on this stuff! I have been really focused on 0.17 so certain things were getting less attention. Port issues are pretty serious though!

[evancz]

Also sorry for the slow response on this stuff! I have been really focused on 0.17 so certain things were getting less attention. Port issues are pretty serious though!