I think that is the intended behaviour. Running Checkconditions on every key can be very intense on ressource especially when having a long page with lots of conditions.

@Carsten,
I agree, but this is not consistent with what is done for (single) numerical question, and maybe text questions.

Oh no, there's two different opinions! I don't know what to do :-)

Change the single numeric to behave like the multiple one ;)

After looking at the way that the existing text, multiple text and numeric questions worked, I tried changing them all so that they only evaluate using "onChange", but it didn't work well. It was too easy for people to click "Next >>" directly from typing in a text box, and thus miss out on a conditional question that only gets displayed after leaving the text box and doing something else. So I've gone for the horribly resource intensive option of using onKeyUp in the multiple numerical question just on the basis that if we've been doing it for all the others we oughtn't discriminate.

I reopened this issue because this behaviour is causing serious problems on IE6 & IE7
I know that everyone hates IE6 but we are supporting it on the survey taking part and until Windows XP is moly wiped from the market there won't be any way around it. Even with a few question the survey is bogging down on IE6/IE7.