>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3589165. --> Reported by: [bnjmnm](https://www.drupal.org/user/2369194) Related to !1083 >>> <h3 id="overview">Overview</h3> <p>@bnjmnm will provide shortly<br> We should revert the fix in <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/canvas/-/work_items/3582883" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/canvas/-/work_items/3582883</a></span> in favor of fixing the underlying problem because</p> <ul> <li>the issue was specific to the datetime widget, but the fix is not at all targeted to it</li> <li>Is documented as logic that will "Remove stale multivalue-field" values in an ajax response... there's so such thing, this is a fresh server response from a form render array. There's nothing "stale", and comments suggesting otherwise will lead to more misconceptions of this being a good place for solutions that should occur elsewhere. </li> <li>Somewhat addressed the <em>symptoms</em> of the issue by broadly removing draggable rows that did not have <code>input[name]</code>, but that row should not be generated by the server to begin with</li> </ul> <h3 id="proposed-resolution">Proposed resolution</h3> <p>Revert the changes in ajax.command.customizations, provide a fix specific to datetime</p> <h3 id="ui-changes">User interface changes</h3> > Related issue: [Issue #3582883](https://www.drupal.org/node/3582883)