Reqiured field - Autopopulated by conditional - Error on submit

Reproduced.

The "bubbles" are provided by the html5 required attribute. The webform jQuery adds/removes this when fields are shown/hidden.

The non-bubble validation message is being generated by the server validation code. This code runs in addition to the jQuery because javascript may be disabled in the browser or the submission may be being made by an attacker. This code apparently does not see the set value properly. I did note that the value is stored in the database if automatic draft saving is enabled. Curious.

Here's what's happening. When the jQuery disables the select list (in order to prevent changes, since I'm pretty sure readonly isn't supported), it causes the data set by the jQuery to not be sent to the server. The server also executes the conditionals, but the validation code looks at the data from the browser, not the conditionals.

The tricky bit is that while I could easily look at the conditionally-set values in Webform's validation, there might be other validation set by other modules or via hook_form_alter(). If I just set the value in the element before calling the validation routines, it may not be in the format expected by the form element because webform normalizes how data is stored into its standard format.

You can try this patch, but without substantial testing for regressions, it isn't ready to be committed.

Also, if someone could work on the issue in the queue about tests not passing (unrelated to this), then that would unblock this issue. I certainly want to make sure tests pass.

Fixed but unable to upload the patch or commit the fix due to limited internet access. Stay tuned.

Do not use patch 4. It's not the right solution.

Patch 4 may work for you in the interim. Test thoroughly.

A rather large patch.

Initially my thought was just to disable validation when a value is set by a conditional. However, this may lead to integrity problems. For example, you might have unique validation on, allowing only one person to have the value set by the conditional. So this requires that Webform be able to put a value back into the form and form_state. This is complicated because every form element is different in how values are represented.

So, this patch:

1. Establishes that any component which is allowed to be used in a conditional with a SET action must implement _webform_action_set_COMPONENT(). Except for markup components. More below on that.
2. In the form validation _webform_client_form_validate(), if the component is being set by a conditional, then the component hook is called to set the $form and $form_state. Unfortunately webform_component_invoke() can't be used for this because it doesn't support reference arguments, and the hooks need to set both the $form and $form_state.
3. A small bug in template_preprocess_webform_element() was fixed, where if a #wrapper_attribute is set and it isn't the class, the component's classes are omitted from the output.
4. The conditional sorter object was enhanced to remember which components were set during the last execution on a submission, and also for markup components, what the markup is being set to.
5. The javascript webform.js was enhanced to properly set and restore the markup component's HTML. This is a new behavior. When a conditional DOESN'T set a markup component, its html is restored to what it was before the conditional executed.
6. Markup components were enhanced to render the conditionally-set value for the form and display. In additional, the original, unset html is rendered as a custom data attribute data-webform-markup.
7. The hidden, number, select, textarea, and textfield components have their set hook implemented. The select component is extra tricky because checkboxes have a unique representation and multiple-select list boxes are also different (an array of values).

Committed to 7.x-4.x and, astonishingly, 8.x.