This bug was introduced when of us developers was unaware of the necessities of strict validation w.r.t. forms. Unfortunately it was only caught after the release. This has since been fixed and the fix will be included in the next release.
This issue is being discussed in the forum in the following topic, which also offers advice on how to temporarily fix this, should strict validation be important to you.
