Jean-Baptiste Kaiser

Okay I get your point, thanks for providing additional examples. I'll mark this as enhancement then, so anyone can open a PR implementing this feature (remember to target the `next`...

Thanks for the detailed report. As you saw, this issue finds its root in a decision made by the `react-hook-form` team, to which we are bound to and left with...

These are good suggestions, thanks! I'd also add the following one: - Fix (and enhance) the support for `readOnly` on all inputs. Indeed, semantically, for this use case where we...

@lvernaillen It seems to me that #9527 actually allows to apply the workaround I suggested [here](https://github.com/marmelab/react-admin/issues/9378#issuecomment-1838126200), which fixes this issue. Can you confirm?

Thanks @lvernaillen for the feedback. You are correct about `AutoCompleteInput`, and actually it looks like we have the same issue with MUI's `Autocomplete` directly. But I agree this is not...

Fixed by https://github.com/marmelab/react-admin/pull/9656

Hi, and thank you for your suggestion. Unfortunately, I don't think this is technically doable in a backwards compatible way. Changing the splat route in `TabbedForm` would be a breaking...

That's a good idea, but I agree the props for `TabbedForm` may start to become a little complex with this addition. Still, I don't know if this use case is...

Thank you for this suggestion. You are right, its' not supported for now. I agree it could be nice to offer that ability. However it's not priority for us, so...

Thank you for your suggestion. Let's wait for feedback from the community to see if this is something that other people would want too :slightly_smiling_face: