Unexpected Auto Row Creation and Weight Display in Multi-Cardinality Fields (UI)
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3584392. --> Reported by: [vipin.mittal18](https://www.drupal.org/user/319716) Related to !902 >>> <p><strong>Description<br> </strong><br> In fields where multiple cardinality is enabled, an issue is observed in the existing 1.x UI behavior.</p> <p>When a user enters a value in a multi-value field, the system automatically creates the next row without requiring any explicit user action (such as clicking &ldquo;+ Add New&rdquo;). Along with this, a row weight field appears automatically, even though no reordering interaction has been performed.<br> <img src="https://www.drupal.org/files/issues/2026-04-13/1.x.gif" width="500" height="600" alt="ui"><img src="https://www.drupal.org/files/issues/2026-04-13/new-ui.gif" width="500" height="600" alt="ui"></p> <p><strong>Acceptance Criteria<br> </strong> </p><ul> <li> <strong>No Automatic Row Creation</strong> <ul> <li>Given a multi-cardinality field</li> <li>When a user enters a value in a row</li> <li>Then a new row should <strong>not</strong> be created automatically</li> <li>And a new row should only appear when explicitly triggered (e.g., via &ldquo;Add another item&rdquo; action)</li> </ul> </li> <li> <strong>Row Weight Visibility Control</strong> <ul> <li>Given a multi-cardinality field</li> <li>When the user has not initiated any reordering action</li> <li>Then the <strong>row weight field should not be displayed</strong></li> </ul> </li> <li> <strong>Consistent Behavior with New UI</strong> <ul> <li>The behavior of multi-cardinality fields in 1.x should align with the new UI implementation</li> <li>No unexpected UI elements (extra rows or weights) should appear</li> </ul> </li> <li> <strong>User Interaction Driven Actions</strong> <ul> <li>All additional rows and reordering controls should be <strong>user-initiated only</strong></li> <li>No implicit triggers based on value entry</li> </ul> </li> </ul> > Related issue: [Issue #3579026](https://www.drupal.org/node/3579026)
issue