You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
Reproduction link
Steps to reproduce
view the diagram in mobile or chorme opening devtool and click the icon of toggling device toolbar,
and click the avg button to render the first diagram ,and then click the detail button to render the second diagram ,and then click the avg button , and then click somewhere where the tootip of the second diagram placed, and then u will find the first diagram will be switched to the second diagram , and u click the grap between two items of the tooltip of the second diagram , and the second diagram will be switched the first diagram
What is expected?
i hope when i click the diagram ,it will be switched unexpected
What is actually happening?
it was switched unexpected
Environment
Info
f2
3.6.3
System
android 9 (MIUI 10.3.6)
Browser
Chrome Dev 83
also i use two different container to contain the canvas , and there the bug is still
The text was updated successfully, but these errors were encountered:
Reproduction link
Steps to reproduce
view the diagram in mobile or chorme opening devtool and click the icon of toggling device toolbar,
and click the avg button to render the first diagram ,and then click the detail button to render the second diagram ,and then click the avg button , and then click somewhere where the tootip of the second diagram placed, and then u will find the first diagram will be switched to the second diagram , and u click the grap between two items of the tooltip of the second diagram , and the second diagram will be switched the first diagram
What is expected?
i hope when i click the diagram ,it will be switched unexpected
What is actually happening?
it was switched unexpected
also i use two different container to contain the canvas , and there the bug is still
The text was updated successfully, but these errors were encountered: