immediate-attribute

Why was “immediate” attribute added to the EditableValueHolders?

It’s to be used to prioritize validation on several EditableValueHolder components in the same form. Imagine a form containing input components with immediate=”true” as well as input components without this attribute. The immediate inputs will be validated during apply request values phase (which is one phase earlier than usual). The non-immediate inputs will be validated … Read more

Trying to understand immediate=”true” skipping inputs when it shouldn’t

With immediate=”true” on the button, the action is indeed invoked during apply request values phase and all the remaining phases are skipped. That’s also the sole point of this attribute: process (decode, validate, update and invoke) the component immediately during apply request values phase. All inputs which do not have immediate=”true” are ignored anyway. Only … Read more