Comment 3 for bug 1787190

This may be due to the fact that someone decided that keeping the net set for orphaned traces. I suspect this change is causing the issue here. The question is do we want this behavior or the old behavior where the net was set to zero and removed when clean up tracks was run. I personally liked the previous behavior but I'm guessing if we change it there will be unhappy users. Anyone of the devs have an opinion on this? Should the priority of this bug report be wishlist or low?