Nico Rehwaldt

> Changing this default behavior would be a breaking change requiring inverting current documentation and verifying that the new default behavior is expected. We have a number of mechanisms in...

_Thanks to @YanaSegal for making me aware of this discussion. Let me try to put it into the big picture of what the modeler does, why._ @YanaSegal there is a...

> why don't we remember this per element / or element type? To add to @barmac's explaination: We remember this per properties panel group, because this is a simple, [no...

@frasalSyc Thanks for the report. This indeed is a bug that has to be fixed in the upstream [token simulation](https://github.com/bpmn-io/bpmn-js-token-simulation) project. From the perspective of `Task A`, there is two...

Moving this to backlog. If you want to help to get this fixed, [bpmn-js-token-simulation](https://github.com/bpmn-io/bpmn-js-token-simulation) is where we need to address this.

> how can an external change make a file dirty? wouldn't they need to save for modeler to see the change? It may happen in the future that certain operations...

> that would not be externally in the sense of outside the modelerer, right? Indeed. I clarified that in the issue description 👍

> Duplicate of https://github.com/camunda/camunda-modeler/issues/2738? Kinda a duplicate, though I attempted to sketch actual behavior we want to implement 🙂; happy to merge both.

Two things we could do, already part of the initial considerations for the feature: However we shall build this on stable foundations - which don't exist as we discussed previously...

Related to https://github.com/nikku/lezer-feel/issues/8, reported and fixed earlier.