Pretty straight forward.
Issue: Double clicking any control (e.g., select one) tricks the app into thinking it was clicked once. E.g., Set up a calculate to something like selected(${test},'yes'), and then quickly double-click ${test}. The calculate will not appropriatly align with the state of ${test}, but it will still allow the form to send (i.e., this bug allows users to bypass requirement logic).
Fix (not really, just a point of reference): Don't make calculates simply refresh on submit. I mean, this may be the solution, in which case great! But, I say this with something very specific in mind: Repeats. Just make sure whatever the solution is works inside of repeats (specifically, and at present, calculates within repeats don't get refreshed like the main survey... sad).
Business impact: Completly breaks form logic, allowing for bad or even "malicious" data to get through which can break down-stream workflows.
