[DISPATCH-792] Freezing and moving nodes is somewhat broken (in either version of console)

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Component/s: Console

Environment

Dispatch and Dispatch plugin at commit e22091b3
Built without libwebsocket, used the old websockify way to connect console
Firefox 51.0.1, Chrome 56.0.2924.87 (64-bit) on Linux

• Assignee: Ernest Allen
• Reporter: Jiri Daněk
• Created: 20/Jun/17 12:46
• Updated: 20/Nov/17 18:33
• Resolved: 01/Jul/17 01:41

Description

If I freeze a node using the right-click menu, then

1) The label in the popup menu randomly switches Freeze/Unfreeze and it is tricky to click the Unfreeze option: https://youtu.be/DwczdnMnnkc

if I am dragging a frozen router node on top of console node, then

2) The legend switches to the other node. I would expect it not to change. https://www.youtube.com/watch?v=HSCxFvFnfTs

3) If I put the nodes exactly on top of each other, I get the following exception in browser log.

Error: <path> attribute d: Expected number, "MNaN,NaNLNaN,NaN".
a	@	d3.min.js?_=1497955959439:1
(anonymous)	@	d3.min.js?_=1497955959439:3
Y	@	d3.min.js?_=1497955959439:1
Aa.each	@	d3.min.js?_=1497955959439:3
Aa.attr	@	d3.min.js?_=1497955959439:3
tick	@	VM79:1125
t	@	d3.min.js?_=1497955959439:1
l.tick	@	d3.min.js?_=1497955959439:4
Rn	@	d3.min.js?_=1497955959439:1
Tn	@	d3.min.js?_=1497955959439:1

Issue 3 is very hard to reproduce, I was able to trigger it two times in hawtio version of console, and then never. Unless it can be figured out from code what could went wrong, it is probably not worth the time to investigate further.