if I put this <input type="hidden" name="id" value="<%= item.id %>"> line in lee file LiveView in handle event repeat html tags :slight_smile: but if I change name to sthid, it works as well, I think id name is one of the parameters we shouldn’t use them in our source. <div class="col-md-3" data-to…

I do not think this is a LiveView bug. <form id="my-form"> <input name="id"> </form> If the form is re-rendered in any way, it will be duplicated in the HTML, as you say. But you can see in the devtools console that document.querySelector("#my-form").id does not return a string (like every ot…

OK this might actually be a Live View bug. I don’t know. I have created an example live view which shows weirdness with name="id" forms and conditionally rendered divs. If you run this and click on “Click Me”, you will see form 1 get duplicated. defmodule MyAppWeb.WeirdLive do use Phoenix.LiveV…

This one is weird for the same underlying reason (input with name=“id”) but is immediately obvious on render: defmodule ClormWeb.WeirdLive do use Phoenix.LiveView def render(assigns) do ~H""" <form :for={index <- 1..3} id={"form-#{index}"}> <input name="id" placeholder={"Form #{i…

I think each input must have a unique id, the name can be whatever but the id has to be unique. You can try this instead <form :for={index <- 1..3} id={"form-#{index}"}> <input name="id" id={"id-#{index}"} placeholder={"Form #{index}"} /> </form> I guess Phoenix, is generating duplic…

[image] I had the weirdest problem with LiveView's change tracking when name attribute has value id Questions I started getting duplicate form elements on DOM updates with leex markup like below and I fixed it by changing hidden input’s name attribute from id t…

LiveView has a problem with input name id

Questions & Help Questions

slouchpie March 17, 2024, 2:51pm 7

Thanks for sharing this. I did try to find existing conversations about it.