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
{{ message }}
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
Long time since this issue was updated. Here's the basics: it's not exactly related to a bug in hyperapp. Rather, the whole set up is very sensitive to differences in timing of when hyperapp renders, when the browser paints, how it relates to setTimeout and requestAnimationFrame....
Since the beginning, it has been a process of trial and error to get something that works consistently across different browsers in different versions of hyperapp. For this reason, I won't be able to maintain the library with the current approach.
I'm currently working on a new version I hope will be much less sensitive to timing issues and much easier to maintain. The downside is that this approach will mean a dramatic shift in how it's used, and more complicated for the user. I hope not too bad, but it needs to be done.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The latest update to hyperapp introduced a bug in transitions, you can notice in the toasts example when toasts are removed. (Janky behavior)
The text was updated successfully, but these errors were encountered: