>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3331377. --> Reported by: [jurgenhaas](https://www.drupal.org/user/168924) >>> <h2>0&#65039;&#8419; Who is here today? Comment in the thread below to introduce yourself! We&rsquo;ll keep the meeting open for 24 hours to allow for all time zones.</h2> <table> <tr> <td>rkoller</td> <td>:wave:</td> </tr> <tr> <td>jurgenhaas</td> <td>J&uuml;rgen here from LakeDrops - full of energy to push ECA further :sunglasses:</td> </tr> <tr> <td>Daniel Speicher</td> <td>Daniel from Lakedrops. Happy New Year!Today, I have to leave earlier.</td> </tr> </table> <h2>1&#65039;&#8419; Do you have any topics to propose for the meeting today? Post in this thread and we&rsquo;ll open threads for them as appropriate. Or you can post them directly in the channel with the next number as an icon. That topic will then turn into a thread for the comments.</h2> <table> </table> <h2>2&#65039;&#8419; Version 1.2 roadmap <a href="https://www.drupal.org/project/issues/search/eca?status%5B%5D=1&amp;status%5B%5D=13&amp;status%5B%5D=8&amp;version%5B%5D=all_1.2.*">https://www.drupal.org/project/issues/search/eca?status%5B%5D=1&amp;status%5B%5D=13&amp;status%5B%5D=8&amp;version%5B%5D=all_1.2.*</a></h2> <table> <tr> <td>rkoller</td> <td>two questions. i am comparing bpmn in eca with bpmn in camunda. has camunda done some modifications and additions compared to bpmn? the properties panel is an aside (what isn&rsquo;t necessarily a good thing in this case) and they have a h3 heading for the properties panel title - both elements are divs with eca &amp; bpmn. and camunda&rsquo;s properties panel is using a button called &sect;details&rdquo; to hide/collapse and show the panel by a click. with bpmn in eca it is accomplished by dragging.and the second question or more of an fyi. i think it might be a good thing to create a meta issue to collect all a11y related issues for eca and bpmn. also creating issues for upstream one&rsquo;s with links and some context to the corresponding upstream issues.&nbsp; i would create the overall meta in the bpmn queue and link all child issues in eca and bpmn.*note i&rsquo;ve posted that first into the main eca channel. but it is more related to version 1.2 roadmap since max suggested to focus on a11y around other things for 1.2&nbsp; i thought it might be better to bring it up in the context of the 1.2 roadmap</td> </tr> <tr> <td>jurgenhaas</td> <td>I'm not tracking what's going on with the Camunda desktop client. You would have to ask those question in their Camunda GitHub projekt I guess.</td> </tr> <tr> <td>jurgenhaas</td> <td>Creating a meta issue in bpmn is OK, I just wonder if it's worth the effort since filtering the issue queue by the a11y tag would give you the same result and you don't run out of sync, if new issues get tagged.</td> </tr> </table> <h2>3&#65039;&#8419; Actions for KeyValue stores, issue needs some clarification and feedback <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/eca/-/work_items/3330979" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/eca/-/work_items/3330979</a></span></h2> <table> <tr> <td>rocketeerbkw</td> <td>Quick PoC this looks to be working well!</td> </tr> <tr> <td>(<em>anonymous</em>)</td> <td><em>Comment Redacted</em></td> </tr> <tr> <td>jurgenhaas</td> <td>Thanks a lot for your first feedback, that's good news.</td> </tr> <tr> <td>jurgenhaas</td> <td>As for next steps, we are not in a hurry</td> </tr> </table> <h2>4&#65039;&#8419; Improve Gateway Support - we need some discussion there <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/eca/-/work_items/3323886" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/eca/-/work_items/3323886</a></span></h2> <table> </table> <h2>5&#65039;&#8419; Adding tours <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/eca_tour/issues/3330804" title="Status: Active">#3330804: [meta] Add tours to improve the onboarding</a></span></h2> <table> <tr> <td>rkoller</td> <td>currently there are only the outlines of the desired tips uploaded. i will work on the corresponding texts as soon as i am done with writing up all the a11y related issues. and in regards of the child issues. does anyone has an idea how to &ldquo;expand&rdquo; a collapsed element simply by a selector? i suppose that won&rsquo;t be possible at all? (ref <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-4"><a href="https://www.drupal.org/project/eca_tour/issues/3330846" title="Status: Postponed">#3330846: Add a tour for the ECA edit model page</a></span> one of the child issues). currently i have only targeted the section elements of the properties panel but it would be neat being able to expand each section and also display&nbsp; tips about fields from within.</td> </tr> <tr> <td>jurgenhaas</td> <td>I guess, the tour module can do that for Drupal Form API elements. But since the property panel is a third party javascript controlled canvas, this may just not be possible. But I don't know for sure.</td> </tr> <tr> <td>rkoller</td> <td>oh that is possible within drupals form api elements?! i havent even tried. will do so later. i was afraid it wouldnt be possible at all.</td> </tr> <tr> <td>jurgenhaas</td> <td>Ah, no. Just tested it on the settings page with the tour item 5-8 if the "Dependency calculation" part were collapsed. That doesn't work either.</td> </tr> <tr> <td>rkoller</td> <td>ah thanks! yep that was my impression that the tours integration is &ldquo;just&rdquo; the show a widget with some bespoke text and either automatically position or have the widget at a predefined approximate position.</td> </tr> <tr> <td>jurgenhaas</td> <td>Could imagine that a smart enhancement to the tour module could just expand all collapsed containers on a page before the tour starts and then restore the previous state, when the tour ends.</td> </tr> <tr> <td>jurgenhaas</td> <td>But I'm not volunteering for implementing it :wink:</td> </tr> <tr> <td>rkoller</td> <td>hahaha you dont have to. you already do more than enough in so many modules. but there isnt much advancement in the tour module currently after the move to shephardjs. it is also discussed to remove it from core in drupal 11 ( or better there is already an issue in the ideas queue). but at the same time development might speed up again in contrib. smustgrave already stepped forward and volunteered to maintain it in contrib and maybe merge it with the tours ui module ( which would be neat ). and he might be also open for such an feature idea. i mean you often have collapsed field sets in drupal.</td> </tr> <tr> <td>jurgenhaas</td> <td>Oh, that sounds interesting. I have to admit that I never really used tours and only enabled it today to review your proposed enhancements. And I thought, hey, that's really helpful.</td> </tr> <tr> <td>jurgenhaas</td> <td>The overhead for providing tours isn't high either, so a lot of users could really benefit from it.</td> </tr> <tr> <td>rkoller</td> <td>yep i totally agree. you could communicate basic concepts for new comers and at the same time provide some guide rails for screen reader users to orient and get a general idea about a page. problem is there is no movement on the create more tours for core meta issue. but in general a tour is perfect. you could provide an overall onboarding explaining basic concepts stepwise. it is also helpful for new features. also to &ldquo;feature&rdquo; them sort of on an update.</td> </tr> <tr> <td>rkoller</td> <td>but in particular for something complex like eca tours is really helpful for anyone tbh</td> </tr> <tr> <td>rkoller</td> <td>i &ldquo;think&rdquo; there is already an issue about collapsed fieldsets and vertical tabs: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/tour/issues/2911208" title="Status: Closed (fixed)">#2911208: Add support for details/vertical tabs</a></span></td> </tr> <tr> <td>rkoller</td> <td>just browsed a bit the tours issue queue and found the aforementioned issue.</td> </tr> <tr> <td>rkoller</td> <td>i&rsquo;ve applied the patch to a 9.5.1 install. in bpmn it doesnt work but on the dependency calculation page you&rsquo;ve tried it expands the fieldset if closed before. neat!</td> </tr> </table>