Add new row button on form errors

[bsramin]

If I try to submit the form with an error, with many rows entered, on rendering the button ends up above the first row.

I am using the latest version and the configuration is "classic":

    'add_label' => $this->translator->trans('company.form.language.addNew', [], 'forms'),
    'entry_type' => CompanyLanguageType::class,
    'allow_add' => true,
    'allow_delete' => true,
    'add_class' => 'custom-add-form',
    'allow_drag_and_drop' => true,
    'drag_and_drop_filter' => 'input',
    'by_reference' => false,
    'display_sort_buttons' => true,
    'error_bubbling' => false,
    'min' => 1,
    'max' => $maxLanguage,

<div class="sm:col-span-full">
        <label for="{{ form.companyLanguage.vars.id }}">{{ form.companyLanguage.vars.label }}</label>
        <div>{{ 'companyLanguage.form.language.help'|trans({}, 'forms') }}</div>
        {{ form_widget(form.companyLanguage) }}
</div>

[Arkounay]

This probably comes from your form theme but it's hard to tell, it could happen for example if a div is added outside of the children when there's an error instead of inside. If you remove your form theme does the error still happen?
I've tried your example but I couldn't reproduce on a fresh install

[bsramin]

I have no form themes configured. I have only worked on the css side. I will try to remove everything unnecessary to see if it is something external interfering.

btw thanks 🙏🏻

[bsramin]

I cannot understand what is going on.
Something in the file ux_collection_form_theme.html.twig doesn't seem OK, apparently.
Activating the display_insert_button, and pressing save with error in the form, shows me the add button in second position, definitely out of place, since it is added to the insert button!

screenshot-20240921-21.17-mkHNJEGy.mp4

I attach the video.

[bsramin]

Probably the error is caused by the forms with Turbo enabled.
We have also this problem when try to change the language in the "new added row".

[Arkounay]

Are you using LiveComponent by any chance? For Turbo by itself it shouldn't create any problem as far as I know, I use it with turbo myself. But for Live Components there is an issue with the way classic collections are handled because UxCollection data are meant to be handled client side by the JS, and then sent to a form, while Live Components expects changes to be synced with ajax requests, it's better to use LiveCollectionType for now if you're using this

If you're not using Live Component, could you share your composer.lock's Turbo version please?

[bsramin]

Yes. I'm using livecomponent 👍🏻
In fact if I remove {{ attributes }} from the div, everything works!

[bsramin]

I think it is correct to report this incompatibility.

[Arkounay]

Thanks @bsramin 👍

Yes you're correct, I've added this to the readme, until I find a proper way to support live components