I do not know what's up with that, but it seems be having a problem casting the boolean output of the previous comparison into the number it expects for the comparison. I don't know why its broken for you, but if it does need to be fixed I think you would have to put a "branch" node to use as a ternary operator (true is 1, false is 0) and feed that into the comparison.