>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3622928. --> Reported by: [pdureau](https://www.drupal.org/user/1903334) Related to !565 !564 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>In <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ui_patterns/-/work_items/3528205" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ui_patterns/-/work_items/3528205</a></span> &amp; <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ui_patterns/-/work_items/3478643" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ui_patterns/-/work_items/3478643</a></span>, we focused on asynchronous load for better performance (no need to create a plugin instance of each source when we are not using the selector).</p> <p>But we also introduced some UX changes:</p> <ul> <li>some already discussed for long and warmly welcomed, like displaying only the default source form when it is a "widget" or the settings summary</li> <li>some with more improvisation, so to be challenged, like the modal system</li> </ul> <p>We need to address those UX topics before releasing 2.0.22.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Let's talk about...</p> <h4>1. Replace <code>details</code> element by a simple "flow" of props ?</h4> <p>Moved to its own issue: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/ui_patterns/issues/3622982" title="Status: Needs work">#3622982: Remove details element in component form?</a></span></p> <h4>2. Open the AJAX inline instead of in modal?</h4> <p>Also discussed in <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ui_patterns/-/work_items/3622509" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ui_patterns/-/work_items/3622509</a></span>.</p> <p>Can we keep the full AJAX logic but load the modal content inside the prop form? As a replacement of the widget form, hiding the "settings" button while we are configuring the sources:<br> <img src="https://www.drupal.org/files/issues/2026-09-14/inlineajax.png" alt="ia"></p> <p>If we keep the settings button in the details summary, let's not forget this in order to avoid some misalignment:</p> <pre>:is(.uip-prop-box, <br>#drupal-off-canvas-wrapper .uip-prop-box) summary .uip-source-selector-toggle--open {<br>&nbsp; height: auto;<br>}</pre><h4>3. How to format <code>PluginSettingsInterface::settingsSummary()</code> ?</h4> <p>(Investigation in progress)</p> <h4>What about slot forms?</h4> <p>Those proposals are bout prop forms, but we have also moved to asynchronous loading for slots. Are those proposals also applicable for slot forms? Is there something to be careful about?</p> <p>For information, Display Builder don't use the slot forms, so it may be addressed in a later follow-up.</p> >>> [!note] Pre-migration files - [inlineajax.png](https://www.drupal.org/files/issues/2026-09-14/inlineajax.png) - [detail-noon-collapsable.png](https://www.drupal.org/files/issues/2026-09-14/detail-noon-collapsable.png) - [clean.png](https://www.drupal.org/files/issues/2026-09-14/clean.png) >>> > Related issue: [Issue #3623623](https://www.drupal.org/node/3623623)