If you have a select field set with "Select or other..." enabled, and it is set as a mandatory field, you cannot leave the field blank and go back a page.
For example, you have page a, page b (ice cream), page c (fruit).
Page A has a checkbox which says do you want ice cream or fruit?
Page B is set to load with a conditional rule if ice cream is selected. User choose ice cream, page b loads. On page b there is a select list (Flavour) with the options
strawberry
chocolate
mint
other...
User changes their mind, they wanted fruit after all! They click "Previous Page" so they can choose fruit instead, Webforms prevents them and says "Flavour field is required."
Without "Select or other..." enabled, users can freely click back through the form without selecting mandatory fields.
Comments
Comment #1
quicksketchThanks for the report, this seems like it may be a slightly tricky problem to solve. Drupal itself always breaks the previous page button in all multipage forms, it was supposed to be impossible until we found a way to hack around it in the 3.x version. Unfortunately select or other doesn't (and shouldn't) use this same hack. We'll need to find a way that Webform can interject it's hack into select_or_other.
Related previous issues:
#588354: no validation for prev button
#226907-60: Patch adding save draft feature
Comment #2
quicksketchThe patch in #966028: warning: Illegal offset type in isset or empty when using "Save draft" button with Select or Other... has corrected this issue.