Entity Reference Content Validation

@maheshv as the reference field is required and limit is set to 4 so if we delete any item from that then it will obvioulsly show error as required field is missing .

I was able to reproduce the described behavior. I noticed that only the first input in the list is being treated as required. So, even if I reorder the list, the error still occurs. Ideally, the field should only be required if none of the inputs in the list are filled out.

I've been investigating this issue in detail and would like to suggest a minimal change that seems to resolve the underlying problem effectively, with minimal impact.

The line 454 in /core/lib/Drupal/Core/Field/WidgetBase.php::formSingleElement() that sets `#required` only on the first item:

// Only the first widget should be required.
'#required' => $delta == 0 && $this->fieldDefinition->isRequired(),

...is likely intended as a fallback to trigger validation when no custom validation is applied. However, in practice — especially for multi-value entity_reference fields using the Autocomplete widget — this causes incorrect validation behavior:

• * If the field is marked as required and multiple values are allowed
• * And the first item is cleared by the user (but others are filled in)
• * The form still throws a "field is required" error, even though a valid value exists

By simply changing that line to

'#required' => FALSE,

..Drupal defers validation to the field-level constraints (e.g., NotNull or custom ones), which correctly validate whether the field as a whole is empty.

This adjustment results in the expected behavior:

• * The form allows submission as long as any value is provided
• * If no value is provided, the form still fails with an appropriate validation error

I’ve tested this change in both new and edit form submissions, and it seems to produce more intuitive behavior without side effects.

Open question:

Is there a deeper reason for this #required line to exist — perhaps to support FAPI-only field types or single-value widgets?

If there are edge cases relying on this, perhaps a conditional fallback could be used instead.

Otherwise, I’d suggest removing the #required here and leaving validation with the constraints system, which appears to handle this more reliably and consistently.

Don't see anything to review so moving back to active.