Specifies when the control will re-initialize on a page.
To re-initalize means the control's element will be removed and a new one will be added to the document.
Additionally, the form entry will be removed and a new one will be added.
Note that re-initializing will always happen between modes when there is a different template used.
And re-initializing will always happen when the control is changed to be a part of a different control collection
i.e moving a control from the main portion of the page to within a group box.
The options are:
modeChange - the control re-initializes when the page mode changes.
- this is the default behaviour.
- this is not an ideal user experience in many cases as it can mean layout shifts and unnecessary rendering.
configChange - the control re-initializes when the control's config changes. Note that config changes can happen on mode change when
the page is re-fetched.
- this gives a good user experience but will mean re-initializing if changes to the control's config are made in admin.
- this is useful if a control's config is complex and catering for that is not worth the effort.
never - no re-initializing occurs.
- controls will need to react to config changes.
- this gives the best user experience.
Specifies when the control will re-initialize on a page. To re-initalize means the control's element will be removed and a new one will be added to the document. Additionally, the form entry will be removed and a new one will be added. Note that re-initializing will always happen between modes when there is a different template used. And re-initializing will always happen when the control is changed to be a part of a different control collection i.e moving a control from the main portion of the page to within a group box.
The options are: modeChange - the control re-initializes when the page mode changes. - this is the default behaviour. - this is not an ideal user experience in many cases as it can mean layout shifts and unnecessary rendering. configChange - the control re-initializes when the control's config changes. Note that config changes can happen on mode change when the page is re-fetched. - this gives a good user experience but will mean re-initializing if changes to the control's config are made in admin. - this is useful if a control's config is complex and catering for that is not worth the effort. never - no re-initializing occurs. - controls will need to react to config changes. - this gives the best user experience.