Nico Rehwaldt

> It would be great if the layouter was able to handle event-based subprocesses. The layouter already supports this (cf. [demo](https://bpmn-io.github.io/bpmn-auto-layout/)), what else would be needed to consider the support...

> IMO, the event-based subprocess should not be collapsed. I agree, could you update the issue accordingly?

From my point of view the overall interaction pattern (including playgrounds and stuff) is blocked by https://github.com/bpmn-io/diagram-js/issues/661. To properly handle keyboard shortcuts we must be browser focus aware and move...

I checked this PR once again, UX wise, as I previously lost one of my reviews :see_no_evil: One thing I found is that clicking anywhere on the canvas with search...

Updated on top of latest DEV branch + pulled in [email protected].

Did some integration testing on the [released changes](https://github.com/bpmn-io/bpmn-js/blob/develop/CHANGELOG.md#17110), and identified potential follow-ups: * https://github.com/bpmn-io/bpmn-js/issues/2232 * https://github.com/bpmn-io/bpmn-js/issues/2233

It now consistently shows up for _all_ elements, in the editor ("edit mode"). We could decide to (1) hide it for all elements, (2) show it for all elements or...

Not addressed on current main, likely related to https://github.com/bpmn-io/bpmn-auto-layout/pull/68#issuecomment-2374445605.  I expect back and forward loops outside of the happy path to always go below other content.

Also interested in getting @till-stadtler's feedback here, our options are: #### Alternative flow below happy path  #### Alternative flow above happy path  ---- Strategy would also apply to...

@till-stadtler you suggest to "loop back" on top, and "loop forward" below?  Why? I'd consistently model happy path first, and everything else below. We'll otherwise run into https://github.com/bpmn-io/bpmn-auto-layout/issues/50#issuecomment-2374504074 and...