This is (I believe) a regression introduced in #2278975: Only display the remove button when there are items in the field. From that issue queue:

What's the reasoning behind not showing the remove button for empty fields?

Ehm... because there's nothing to remove?

Ha, that's true initially. But once the editor starts adding items to multiple-value fields, then there are things to remove. Form state is changing throughout the node/add process, but the module only reacts to the initial empty node object.

Screenshot of new node form showing need for Remove button

CommentFileSizeAuthor
#1 field_remove_item-2400955-button_for_new_entities.patch1.96 KBLes Lim
field_remove_item-explanation.jpg147.13 KBLes Lim
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Les Lim’s picture

Les Lim
he/they
Primary language English
CreditAttribution: Les Lim commented
Status: Active » Needs review
FileSize
field_remove_item-2400955-button_for_new_entities.patch1.96 KB

Patch removes conditional check of items count.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Status: Needs review » Reviewed & tested by the community

Works perfectly for me, but #2278975: Only display the remove button when there are items in the field is the opposite. Well, ideally $context['items'] would be filled when we create new entities, but as long that doesn't work, we need to keep the current version, I would argue.

  • pcambra committed ebf3e74 on 7.x-1.x authored by Les Lim 
    Issue #2400955 by Les Lim, dawehner: Show remove button when creating...
pcambra’s picture

pcambra
he/him
Primary language Spanish
Location Asturies
CreditAttribution: pcambra as a volunteer commented
Status: Reviewed & tested by the community » Fixed

Thank you both!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.