Greg Johnston

Just leaving an update: 0.7 is a significant enough rewrite that the functions this PR modifies in `leptos_reactive` are not used (that entire crate may no longer be in existence...

PR welcome to add it. Another possibility is to use a resource, which does allow mutation.

1) You should use `.get()` ([see example](https://codesandbox.io/p/devbox/leptos-node-ref-remount-forked-c6x2n8?file=%2Fsrc%2Fmain.rs%3A4%2C28)) 2) `.on_load()`'s behavior of only working once should be documented properly. 2) The warning is safe to ignore in this case, of course,...

Oof. Is there a reason to think this might be a Chrome bug, or Chrome being spec-non-compliant? Comparison with other browsers would be good. The W3C [UI Events spec](https://w3c.github.io/uievents/#event-type-keydown) is...

Yeah I'll be honest I'm not sure the best way to deal with this. From looking around a little, my impression is that this is a long-standing Chrome thing that...

https://github.com/leptos-rs/leptos/assets/286622/93db0300-927f-474d-86c1-a83768a7b72e

Oh, I see. Your example doesn't use the ``. The coordination between the error value stored in the route and the error value stored in the server action is handled...

> Indeed, in my small example, it didn't work because the Router is missing. But my actual application uses a Router. > > It seems it also doesn't work when...

This error handling setup is not currently implemented for custom error types. When a server action is created, it looks for `ServerFnUrlError` in context https://github.com/leptos-rs/leptos/blob/ffcf3c2952240598ab9f019a75c77c9145965670/leptos_server/src/action.rs#L317-L324 It does not look directly...

Thanks very much for the contribution, and for your patience through all the back and forth!