Yep appears to be a bug. It was introduced between 1.0.3 and 1.0.4 it appears. 1.0.3 reacts as expected the trace stops at the first connection when moved from top to bottom.
in 1.0.4 and later it changes the entire trace which looks to be incorrect..
You need to open an issue on github here:
Going back to 1.0.3 should work around the problem til it gets fixed I expect.
Peter