The Export SVG button is not working

Moving this to the correct project as this is not an ECA issue but something to do with the bpmn_io UI module. Looks like one of the latest updates from the upstream library broke that SVG export. All components for this feature are from the upstream library, so we can only report this to them and hope that they will fix it in their code.

When it comes to action buttons, they're all required in the context of an individual model. When using the Gin admin theme instead of Claro, they will be in a dropdown and only the save button is visible as a prominent component. Would be great if Claro would adopt that feature eventually as well.

I probably found a solution already. We have to explicitly set the focus to the canvas and then use a promise to write the SVG file.

Please test the above commit, it should be working after you're cleaned your browser cache and reloaded the page.

Sorry, I didn't know it wasn't an ECA topic.
Thanks for reporting it to the bpmn_io UI module developers!

@tetatu no worries. Have you had a chance to test my fix as well?

Yes, and Thank you!

I recently replaced the BPMN.iO 2.0.6 version with Composer for the 2.1.x-dev version and the SVG button is now working.
What I don't understand is that I exported and then imported the BPMN.iO 2.0.6 state with the
Configuration management module, and after replacing it with the 2.1.x-dev version, Configuration management did not detect any changes and the version of the modules does not appear for BPMN.iO, like for the other modules.

UI. Beginners but enthusiastic Drupal users who are also beginners in programming can help with the development of ECA? I don't understand why Rules still has 100+ thousand users, when the version for Drupal 10 is very incomplete compared to the Drupal 7 version. ECA varies around 6-8 thousand, although in theory (looking at the video demonstrations and descriptions, it already knows everything that the old Rules knew...).

Thank you @tetatu for your feedback. Testing things like the fix in here doesn't necessarily require a composer update for the dev release. We usually do that with patches. So, you keep your code base as it is, and you can temporarily apply the fix with separate commands. Configuration management doesn't have to do with this part.

Beginners but enthusiastic Drupal users who are also beginners in programming can help with the development of ECA?

Yes, absolutely. If you hang out in the issue queues of ECA and bpmn_io, there are plenty of issues that also beginners can deal with. And we do have a very active #ECA channel on Drupal Slack where you can chat with hundreds of other users and get help when you want to know something new for testing, development or debugging, etc.

But if you want to help us otherwise, e.g. with documentation or what else, then ping me on Slack and we can find something for you.

And why the rules module is still popular? I'm sure there are important reasons, most likely it's the migration cost if sites have to rebuild their rules into something new. There has recently been an issue, where users discussed this topic: 💬 A honest comparison / contrast of ECA vs Rules? Active

Again, thank you for reporting the bug and testing the fix.

Back ported to 2.0.x