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
Browsers you attempted to reproduce this bug on (the more the merrier): chrome
Does the problem persist after removing "assets/node_modules" and trying again? Yes/no: no
Actual behavior
Found an inconsistent behavior while using forms bindings & JS commands, binding a JS command to phx-change doesnt work well on recovery cause the JS command doesnt get evaluated properly and pushes a non-parsed event, I added a minimal example, try disconnecting and reconnecting to see the error. does using JS commands with form bindings is something that I should not be doing? or is it an issue?
Environment
Actual behavior
Found an inconsistent behavior while using forms bindings & JS commands, binding a JS command to phx-change doesnt work well on recovery cause the JS command doesnt get evaluated properly and pushes a non-parsed event, I added a minimal example, try disconnecting and reconnecting to see the error. does using JS commands with form bindings is something that I should not be doing? or is it an issue?
Expected behavior
JS.push will always result with the same event reaching the server, no matter if the form is recovering or just changed.
The text was updated successfully, but these errors were encountered: