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
When I trigger the animation (by setting a new Animation.State in my model) in the UrlChanged Msg of Browser.application (newly introduced in 0.19), these animations are never run, even if the elements, to be animated, are already in the DOM.
Setup was co-checked by manually triggering the Animation via onClick Event, in order to make sure there are no other problems in the animation-mechanism, which worked fine.
Probably it is not a problem in this package. Maybe there is an exception rule in the elm runtime, that does not update the views in the two Routing Messages (LinkClicked and UrlChanged) of Browser.application?
The text was updated successfully, but these errors were encountered:
When I trigger the animation (by setting a new Animation.State in my model) in the UrlChanged Msg of Browser.application (newly introduced in 0.19), these animations are never run, even if the elements, to be animated, are already in the DOM.
Setup was co-checked by manually triggering the Animation via onClick Event, in order to make sure there are no other problems in the animation-mechanism, which worked fine.
Probably it is not a problem in this package. Maybe there is an exception rule in the elm runtime, that does not update the views in the two Routing Messages (LinkClicked and UrlChanged) of Browser.application?
The text was updated successfully, but these errors were encountered: