Mindmap editing functionality is not working when we apply the CSS style **scale** to the parent container

GoJS
1

Mindmap editing functionality is not working when we apply the CSS style scale to the parent container. My code is given below:

<div id="sample" *style="scale:0.8;"*>
  <div id="myDiagramDiv" style="border: 1px solid black; width: 100%; height: 300px; position: relative; -webkit-tap-highlight-color: rgba(255, 255, 255, 0);"><canvas tabindex="0" width="1317" height="372" style="position: absolute; top: 0px; left: 0px; z-index: 2; user-select: none; touch-action: none; width: 1054px; height: 298px;"></canvas><div style="position: absolute; overflow: auto; width: 1054px; height: 298px; z-index: 1;"><div style="position: absolute; width: 1px; height: 1px;"></div></div></div>`

Is there any way to resolve this issue? If yes, please share more details.

2

Thanks for reporting the problem. We’ll look into it.

3

The canvas coordinates cannot easily account for transforms made on the page. Why do this, rather than setting the Diagram.scale?

4

We have multiple components in our canvas. So that we need to set scale for Mindmap. When zooming the canvas Mindmap functionality is not working. A snap of our project is given here:

Capture
Capture1777Ă—803 84.3 KB

5

What are you using to render and manage that overall diagram and each component in it? How “live” is each component? What happens when a user resizes a component?

6

We use angular render to render the diagram.
Actually the mind map is created using GoJS and implemented in angular way to create as a component and it is directly implemented as a node in rete.
This is an angular based Project. Each component is a node which is created by using rete.js with angular plugin. There is a Node resizing functionality in every node and if a user resizes a node, the component will resize and shows a scroll bar.
When we zoom in the area outside the node (infinite canvas), then the functionalities of the Mind map node is not working.

7

We’re looking into this.

1 Like
8

OK, the simple case involving scaling might be fixed in the next v3.0 release, which should be soon.

9

Thankyou for the update.