Oh, I’m sorry, I was confused and thought that was due to the results page.
You are right, that shouldn’t be triggered. I quickly checked, and there seems to be a type coercion issue within the core script, I can replicate this.
Long story short, the script checks if the option is disabled, and the option is sent as either a 0 (if disabled) or 1 (if enabled). However by mistake it’s converted to a string, therefore instead of 0 or 1 the value is “0” or “1”. And in javascript deals with that in a funny way, as 0 is coerced to a boolean false, but “0” is a boolean true – therefore it thinks the option is enabled.
I will get back to you in an hour or so, I think I can patch this real quick and send you a beta copy to test.