Invalid Nodes are not described when used in a circuit

[vidalia]

In Vidalia 0.1.4, part of the Tor Bundle 0.2.0.28-rc on Windows XP Home Edition, if "AllowInvalidNodes?" options are set, and such a node is used in a circuit, Vidalia will display the circuit in the Tor Network Map window.

Previously (0.1.3), when a circuit with an invalid node is clicked on, information on all the nodes, even if only to state that a node was Offline, would appear to the right of the circuit list.

However, in the current version (0.1.4), if a circuit with an invalid node is clicked on, Vidalia will ignore the invalid node, displaying information only on valid nodes. This can lead to, for example, a circuit clearly showing three nodes, with only two of the nodes described on the right.

While it may be reasonable to remove invalid/offline nodes from the list on the left side of the Tor Network Map, if such a node is used in a circuit, Vidalia should still display the network's opinion as to if the node is valid or not, and where the node's geographic location is.

[edmanm]

Vidalia does not (and never has) actively filtered invalid nodes. Can you give some examples of invalid nodes to reproduce this behavior?

[vidalia]

Screenshot Showing Incorrect Behavior In Vidalia 0.1.5

[vidalia]

Comparison: Correct Behavior of Vidalia 0.1.3 Versus Incorrect Behavior of Vidalia 0.1.5; both instances connected to the same Tor client

[vidalia]

I will add that the title of this bug no longer seems to match the problem that is occuring; whistlersmother is a valid Tor Router, whileas to the best of my knowledge this had only occured with invalid nodes before today.