Control SAP SE Base Class for Controls. Controls provide the following features: <ul> <li>Rendering: the <code>RenderManager</code> only expects instances of class <code>Control</code> in its {@link sap.ui.core.RenderManager#renderControl renderControl} method. By convention, each control class has an associated static class that takes care of rendering the control (its 'Renderer').</li> <li>show / hide: a control can be hidden, although it is still part of the control tree, see property {@link #getVisible visible}</li> <li>local busy indicator: marks a control visually as 'busy', see properties {@link #getBusy busy} and {@link #getBusyIndicatorDelay busyIndicatorDelay}</li> <li>field groups: by assigning the same group ID to a set of editable controls, they form a group which can be validated together. See property {@link #getFieldGroupIds fieldGroupIds} and event {@link #event:validateFieldGroup validateFieldGroup}. The term field was chosen as most often this feature will be used to group editable fields in a form.</li> See the documentation for {@link topic:5b0775397e394b1fb973fa207554003e Field Groups} for more details. <li>custom style classes: all controls allow to add custom CSS classes to their rendered DOM without modifying their renderer code. See methods {@link #addStyleClass addStyleClass}, {@link #removeStyleClass removeStyleClass}, {@link #toggleStyleClass toggleStyleClass} and {@link #hasStyleClass hasStyleClass}. The necessary implementation is encapsulated in {@link sap.ui.core.CustomStyleClassSupport CustomStyleClassSupport} and can be applied to selected element classes as well.</li> <li>browser events: by calling the methods {@link #attachBrowserEvent attachBrowserEvent} and {@link #detachBrowserEvent detachBrowserEvent}, consumers can let the control class take care of registering / de-registering a given set of event listeners to the control's root DOM node. The framework will adapt the registration whenever the DOM node changes (e.g. before or after rendering or when the control is destroyed).</li> </ul> See section "{@link topic:91f1703b6f4d1014b6dd926db0e91070 Developing OpenUI5/SAPUI5 Controls}" in the documentation for an introduction to control development. sap.ui.core/Element Whether the control is currently in blocked state. The blocked property is deprecated. There is no accessibility support for this property. Blocked controls should not be used inside Controls, which rely on keyboard navigation, e.g. List controls. Whether the control is currently in busy state. The delay in milliseconds, after which the busy indicator will show up for this control. The size of the BusyIndicator. For controls with a width smaller 3rem a <code>sap.ui.core.BusyIndicatorSize.Small</code> should be used. If the size could vary in width and the width could get smaller than 3rem, the <code>sap.ui.core.BusyIndicatorSize.Auto</code> option could be used. The default is set to <code>sap.ui.core.BusyIndicatorSize.Medium</code> For a full screen BusyIndicator use <code>sap.ui.core.BusyIndicatorSize.Large</code>. Whether the control should be visible on the screen. If set to false, a placeholder will be rendered to mark the location of the invisible control in the DOM of the current page. The placeholder will be hidden and have zero dimensions (<code>display: none</code>). Also see {@link module:sap/ui/core/InvisibleRenderer InvisibleRenderer}. The IDs of a logical field group that this control belongs to. All fields in a logical field group should share the same <code>fieldGroupId</code>. Once a logical field group is left, the <code>validateFieldGroup</code> event is fired. For backward compatibility with older releases, field group IDs are syntactically not limited, but it is suggested to use only valid {@link sap.ui.core.ID}s. See {@link #attachValidateFieldGroup} or consult the {@link topic:5b0775397e394b1fb973fa207554003e Field Group} documentation. Event is fired if a logical field group defined by <code>fieldGroupIds</code> of a control was left or when the user explicitly pressed the key combination that triggers validation. By default, the <code>RETURN</code> key without any modifier keys triggers validation, see {@link #triggerValidateFieldGroup}. Listen to this event to validate data of the controls belonging to a field group. See {@link #setFieldGroupIds}, or consult the {@link topic:5b0775397e394b1fb973fa207554003e Field Group} documentation. field group IDs of the logical field groups to validate