Open zaceno opened 6 years ago
@zaceno Any idea where the bug is?
@jorgebucaran I opened an issue in Hyperapp with what I've figured out so far. I believe it's a bug in 1.2.6.
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.
The latest update to hyperapp introduced a bug in transitions, you can notice in the toasts example when toasts are removed. (Janky behavior)