What happened?
When View → Regions is toggled on, the region hulls (soft-coloured outlines around each region of operators during execution) appear only on the mini-map in the bottom-right corner. The main workflow canvas stays empty no matter how the checkbox is flipped.
Expected: the toggle should drive both surfaces — hulls visible on the main canvas when on, hidden when off.
Root cause: the main editor permanently carries a hide-region CSS class that forces display: none on every region element, while toggleRegion() only flips a body/visibility attribute. The mini-map has no such class, so the same model elements render there. Regression from #4495
How to reproduce?
- Open a workflow with at least two connected operators.
- Run it so the backend emits region updates.
- Toggle View → Regions on.
- Observe: hulls show on the mini-map but never on the main canvas.
Branch
main
Commit Hash (Optional)
dd39f93
What browsers are you seeing the problem on?
No response
Relevant log output
What happened?
When View → Regions is toggled on, the region hulls (soft-coloured outlines around each region of operators during execution) appear only on the mini-map in the bottom-right corner. The main workflow canvas stays empty no matter how the checkbox is flipped.
Expected: the toggle should drive both surfaces — hulls visible on the main canvas when on, hidden when off.
Root cause: the main editor permanently carries a
hide-regionCSS class that forcesdisplay: noneon every region element, whiletoggleRegion()only flips abody/visibilityattribute. The mini-map has no such class, so the same model elements render there. Regression from #4495How to reproduce?
Branch
main
Commit Hash (Optional)
dd39f93
What browsers are you seeing the problem on?
No response
Relevant log output