Brian Cardarella
Brian Cardarella
Is this under consideration at all? I'd like to know if I should continue with the motion JS command wrapper, without this feature I don't think it's worth continuing.
I spoke with @chrismccord and I want to provide my understanding of what Chris's position is (if I'm misunderstanding this please correct me) as well as my feedback on what...
@SteffenDE have your update delete the element from the DOM
@SteffenDE no I'm talking about how LV can patch when another async operation acting upon that element is already in-flight.
@SteffenDE yes but it should be up to the developer to make that call. I described the API here https://github.com/phoenixframework/phoenix_live_view/issues/3516#issuecomment-2486040289
And what happens in the event that the dispatched event takes say 1 hour to complete? Locking the entire DOM to wait for a single async event to complete doesn't...
@SteffenDE it doesn't need to be an animation, any async event. And I really don't think that LV core should be limiting API access based upon their opinions of UI...
My use case is I want to dispatch very long running animations and not have inbound patch updates cause jank or otherwise disrupt that animation.
I'll add: while allowing other nodes in the DOM to continue to receive patches.
@SteffenDE just three days ago you were in favor of this, you yourself opened the issue. I'm not sure what happened here but clearly there was activity and conversation that...