Skip to content

[LiveComponent] No selected <option> treated differently when submitted from a Live Component #767

@benr77

Description

@benr77

Using 2.x.dev which includes #728, and latest Stimulus Bridge 3.2.2.

This is a bit of a weird one. If I for example use an EntityType or a ChoiceType to generate a <select> element, and I do not use a placeholder value, we will get HTML such as:

<select>
  <option value="1">Option One</option>
  <option value="2">Option Two</option>
</select>

When this is rendered by the browser, if no option is selected, and there is no placeholder option, the first option "Option One" will be shown, but without a selected attribute.

In a normal Symfony form in a standard POST submission, the browser seems to send the "Option One" as though the user had physically selected it. For example, a NotBlank() validation would PASS.

The Problem

If you then move this form into a LiveComponent, the behaviour changes.

Submitting the form without touching the select element does NOT assume that the first element is implicitly selected, and null is sent as the select field's value.

This means any NotBlank() validation FAILS, even though as far as the user is concerned, the "Option One" was selected (it was shown as the selected entry in the form field, even though they didn't physically click on it).

This then makes a mess when submitting the form, as you get a validation error, and you have to go and click and select the option that is already, as far as you the user is concerned, selected.

I'm guessing this is to do with the way that the Live Component's JS submits the form, and that this is differing in this case with a standard browser form submit.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions