@openui5/sap.ui.core 1.107.1 → 1.108.1

package/src/sap/ui/core/RenderManager.js

@@ -186,7 +186,7 @@ sap.ui.define([
 	 *
 	 * @extends Object
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 * @alias sap.ui.core.RenderManager
 	 * @public
 	 */
@@ -693,107 +693,6 @@ sap.ui.define([
 			return this;
 		};
 
-		/**
-		 * Collects accessibility related attributes for an <code>Element</code> and renders them as part of
-		 * the currently rendered DOM element.
-		 *
-		 * See the WAI-ARIA specification for a general description of the accessibility related attributes.
-		 * Attributes are only rendered when the accessibility feature is activated in the UI5 runtime configuration.
-		 *
-		 * The values for the attributes are collected from the following sources (last one wins):
-		 * <ol>
-		 * <li>from the properties and associations of the given <code>oElement</code>, using a heuristic mapping
-		 *     (described below)</li>
-		 * <li>from the <code>mProps</code> parameter, as provided by the caller</li>
-		 * <li>from the parent of the given <code>oElement</code>, if it has a parent and if the parent implements
-		 *     the method {@link sap.ui.core.Element#enhanceAccessibilityState enhanceAccessibilityState}</li>
-		 * </ol>
-		 * If no <code>oElement</code> is given, only <code>mProps</code> will be taken into account.
-		 *
-		 *
-		 * <h3>Heuristic Mapping</h3>
-		 * The following mapping from properties/values to ARIA attributes is used (if the element does have such properties):
-		 * <ul>
-		 * <li><code>editable===false</code> => <code>aria-readonly="true"</code></li>
-		 * <li><code>enabled===false</code> => <code>aria-disabled="true"</code></li>
-		 * <li><code>visible===false</code> => <code>aria-hidden="true"</code></li>
-		 * <li><code>required===true</code> => <code>aria-required="true"</code></li>
-		 * <li><code>selected===true</code> => <code>aria-selected="true"</code></li>
-		 * <li><code>checked===true</code> => <code>aria-checked="true"</code></li>
-		 * </ul>
-		 *
-		 * In case of the <code>required</code> property, all label controls which reference the given element
-		 * in their <code>labelFor</code> relation are additionally taken into account when determining the
-		 * value for the <code>aria-required</code> attribute.
-		 *
-		 * Additionally, the associations <code>ariaDescribedBy</code> and <code>ariaLabelledBy</code> are used to
-		 * determine the lists of IDs for the ARIA attributes <code>aria-describedby</code> and
-		 * <code>aria-labelledby</code>.
-		 *
-		 * Label controls that reference the given element in their <code>labelFor</code> relation are automatically
-		 * added to the <code>aria-labelledby</code> attribute.
-		 *
-		 * Note: This function is only a heuristic of a control property to ARIA attribute mapping. Control developers
-		 * have to check whether it fulfills their requirements. In case of problems (for example the <code>RadioButton</code> has a
-		 * <code>selected</code> property but must provide an <code>aria-checked</code> attribute) the auto-generated
-		 * result of this function can be influenced via the parameter <code>mProps</code> as described below.
-		 *
-		 * The parameter <code>mProps</code> can be used to either provide additional attributes which should be rendered
-		 * and/or to avoid the automatic generation of single ARIA attributes. The 'aria-' prefix will be prepended
-		 * automatically to the keys (Exception: Attribute <code>role</code> does not get the prefix 'aria-').
-		 *
-		 *
-		 * Examples:<br>
-		 * <code>{hidden : true}</code> results in <code>aria-hidden="true"</code> independent of the presence or
-		 * absence of the visibility property.<br>
-		 * <code>{hidden : null}</code> ensures that no <code>aria-hidden</code> attribute is written independent
-		 * of the presence or absence of the visibility property.<br>
-		 *
-		 * The function behaves in the same way for the associations <code>ariaDescribedBy</code> and <code>ariaLabelledBy</code>.
-		 * To append additional values to the auto-generated <code>aria-describedby</code> and <code>aria-labelledby</code>
-		 * attributes, the following format can be used:
-		 * <pre>
-		 *   {describedby : {value: "id1 id2", append: true}} =>  aria-describedby = "ida idb id1 id2"
-		 * </pre>
-		 * (assuming that "ida idb" is the auto-generated part based on the association <code>ariaDescribedBy</code>).
-		 *
-		 * @param {sap.ui.core.Element}
-		 *            [oElement] The <code>Element</code> whose accessibility state should be rendered
-		 * @param {object}
-		 *            [mProps] A map of additional properties that should be added or changed.
-		 * @returns {this} Reference to <code>this</code> in order to allow method chaining
-		 * @public
-		 * @function
-		 */
-		this.accessibilityState = this.writeAccessibilityState;
-
-		/**
-		 * Writes either an &lt;img&gt; tag for normal URI or a &lt;span&gt; tag with needed properties for an icon URI.
-		 *
-		 * Additional classes and attributes can be added to the tag with the second and third parameter.
-		 * All of the given attributes are escaped when necessary for security consideration.
-		 *
-		 * When an &lt;img&gt; tag is rendered, the following two attributes are added by default
-		 * and can be overwritten with corresponding values in the <code>mAttributes</code> parameter:
-		 * <ul>
-		 * <li><code>role: "presentation"</code></Li>
-		 * <li><code>alt: ""</code></li>
-		 * </ul>
-		 *
-		 * <b>Note:</b> This function requires the {@link sap.ui.core.IconPool} module. Ensure that the module is
-		 * loaded before this function is called to avoid syncXHRs.
-		 *
-		 * @param {sap.ui.core.URI} sURI URI of an image or of an icon registered in {@link sap.ui.core.IconPool}
-		 * @param {array|string} [aClasses] Additional classes that are added to the rendered tag
-		 * @param {object} [mAttributes] Additional attributes that will be added to the rendered tag.
-		 * Currently the attributes <code>class</code> and <code>style</code> are not allowed
-		 * @returns {this} Reference to <code>this</code> in order to allow method chaining
-		 * @public
-		 * @function
-		 */
-		this.icon = this.writeIcon;
-
-
 		//#################################################################################################
 		// Semantic Rendering Interface for DOM Based Rendering
 		//#################################################################################################
@@ -931,8 +830,10 @@ sap.ui.define([
 				var oEvent = new jQuery.Event("BeforeRendering");
 				// store the element on the event (aligned with jQuery syntax)
 				oEvent.srcControl = oControl;
+				oControl._bOnBeforeRenderingPhase = true;
 				oControl._handleEvent(oEvent);
 			} finally {
+				oControl._bOnBeforeRenderingPhase = false;
 				bLocked = false;
 			}
 		}
@@ -1723,7 +1624,7 @@ sap.ui.define([
 	 * <code>aria-labelledby</code>.
 	 *
 	 * Label controls that reference the given element in their <code>labelFor</code> relation are automatically
-	 * added to the <code>aria-labelledby</code> attributes.
+	 * added to the <code>aria-labelledby</code> attribute.
 	 *
 	 * Note: This function is only a heuristic of a control property to ARIA attribute mapping. Control developers
 	 * have to check whether it fulfills their requirements. In case of problems (for example the <code>RadioButton</code> has a
@@ -1755,9 +1656,8 @@ sap.ui.define([
 	 *            [mProps] A map of additional properties that should be added or changed.
 	 * @returns {this} Reference to <code>this</code> in order to allow method chaining
 	 * @public
-	 * @deprecated Since 1.92. Instead use {@link sap.ui.core.RenderManager#accessibilityState} of the {@link sap.ui.core.RenderManager Semantic Rendering API}.
 	 */
-	RenderManager.prototype.writeAccessibilityState = function(oElement, mProps) {
+	RenderManager.prototype.accessibilityState = function(oElement, mProps) {
 		if (!Configuration.getAccessibility()) {
 			return this;
 		}
@@ -1855,12 +1755,87 @@ sap.ui.define([
 		return this;
 	};
 
+	/**
+	 * Collects accessibility related attributes for an <code>Element</code> and renders them as part of
+	 * the currently rendered DOM element.
+	 *
+	 * See the WAI-ARIA specification for a general description of the accessibility related attributes.
+	 * Attributes are only rendered when the accessibility feature is activated in the UI5 runtime configuration.
+	 *
+	 * The values for the attributes are collected from the following sources (last one wins):
+	 * <ol>
+	 * <li>from the properties and associations of the given <code>oElement</code>, using a heuristic mapping
+	 *     (described below)</li>
+	 * <li>from the <code>mProps</code> parameter, as provided by the caller</li>
+	 * <li>from the parent of the given <code>oElement</code>, if it has a parent and if the parent implements
+	 *     the method {@link sap.ui.core.Element#enhanceAccessibilityState enhanceAccessibilityState}</li>
+	 * </ol>
+	 * If no <code>oElement</code> is given, only <code>mProps</code> will be taken into account.
+	 *
+	 *
+	 * <h3>Heuristic Mapping</h3>
+	 * The following mapping from properties/values to ARIA attributes is used (if the element does have such properties):
+	 * <ul>
+	 * <li><code>editable===false</code> => <code>aria-readonly="true"</code></li>
+	 * <li><code>enabled===false</code> => <code>aria-disabled="true"</code></li>
+	 * <li><code>visible===false</code> => <code>aria-hidden="true"</code></li>
+	 * <li><code>required===true</code> => <code>aria-required="true"</code></li>
+	 * <li><code>selected===true</code> => <code>aria-selected="true"</code></li>
+	 * <li><code>checked===true</code> => <code>aria-checked="true"</code></li>
+	 * </ul>
+	 *
+	 * In case of the <code>required</code> property, all label controls which reference the given element
+	 * in their <code>labelFor</code> relation are additionally taken into account when determining the
+	 * value for the <code>aria-required</code> attribute.
+	 *
+	 * Additionally, the associations <code>ariaDescribedBy</code> and <code>ariaLabelledBy</code> are used to
+	 * determine the lists of IDs for the ARIA attributes <code>aria-describedby</code> and
+	 * <code>aria-labelledby</code>.
+	 *
+	 * Label controls that reference the given element in their <code>labelFor</code> relation are automatically
+	 * added to the <code>aria-labelledby</code> attribute.
+	 *
+	 * Note: This function is only a heuristic of a control property to ARIA attribute mapping. Control developers
+	 * have to check whether it fulfills their requirements. In case of problems (for example the <code>RadioButton</code> has a
+	 * <code>selected</code> property but must provide an <code>aria-checked</code> attribute) the auto-generated
+	 * result of this function can be influenced via the parameter <code>mProps</code> as described below.
+	 *
+	 * The parameter <code>mProps</code> can be used to either provide additional attributes which should be rendered
+	 * and/or to avoid the automatic generation of single ARIA attributes. The 'aria-' prefix will be prepended
+	 * automatically to the keys (Exception: Attribute <code>role</code> does not get the prefix 'aria-').
+	 *
+	 *
+	 * Examples:<br>
+	 * <code>{hidden : true}</code> results in <code>aria-hidden="true"</code> independent of the presence or
+	 * absence of the visibility property.<br>
+	 * <code>{hidden : null}</code> ensures that no <code>aria-hidden</code> attribute is written independent
+	 * of the presence or absence of the visibility property.<br>
+	 *
+	 * The function behaves in the same way for the associations <code>ariaDescribedBy</code> and <code>ariaLabelledBy</code>.
+	 * To append additional values to the auto-generated <code>aria-describedby</code> and <code>aria-labelledby</code>
+	 * attributes, the following format can be used:
+	 * <pre>
+	 *   {describedby : {value: "id1 id2", append: true}} =>  aria-describedby = "ida idb id1 id2"
+	 * </pre>
+	 * (assuming that "ida idb" is the auto-generated part based on the association <code>ariaDescribedBy</code>).
+	 *
+	 * @param {sap.ui.core.Element}
+	 *            [oElement] The <code>Element</code> whose accessibility state should be rendered
+	 * @param {object}
+	 *            [mProps] A map of additional properties that should be added or changed.
+	 * @returns {this} Reference to <code>this</code> in order to allow method chaining
+	 * @public
+	 * @deprecated Since 1.92. Instead use {@link sap.ui.core.RenderManager#accessibilityState} of the {@link sap.ui.core.RenderManager Semantic Rendering API}.
+	 * @function
+	 */
+	RenderManager.prototype.writeAccessibilityState = RenderManager.prototype.accessibilityState;
+
 
 	/**
 	 * Writes either an &lt;img&gt; tag for normal URI or a &lt;span&gt; tag with needed properties for an icon URI.
 	 *
 	 * Additional classes and attributes can be added to the tag with the second and third parameter.
-	 * All of the given attributes are escaped for security consideration.
+	 * All of the given attributes are escaped when necessary for security consideration.
 	 *
 	 * When an &lt;img&gt; tag is rendered, the following two attributes are added by default
 	 * and can be overwritten with corresponding values in the <code>mAttributes</code> parameter:
@@ -1869,14 +1844,17 @@ sap.ui.define([
 	 * <li><code>alt: ""</code></li>
 	 * </ul>
 	 *
+	 * <b>Note:</b> This function requires the {@link sap.ui.core.IconPool} module. Ensure that the module is
+	 * loaded before this function is called to avoid syncXHRs.
+	 *
 	 * @param {sap.ui.core.URI} sURI URI of an image or of an icon registered in {@link sap.ui.core.IconPool}
 	 * @param {array|string} [aClasses] Additional classes that are added to the rendered tag
-	 * @param {object} [mAttributes] Additional attributes that will be added to the rendered tag
+	 * @param {object} [mAttributes] Additional attributes that will be added to the rendered tag.
+	 * Currently the attributes <code>class</code> and <code>style</code> are not allowed
 	 * @returns {this} Reference to <code>this</code> in order to allow method chaining
 	 * @public
-	 * @deprecated Since 1.92. Instead use {@link sap.ui.core.RenderManager#icon} of the {@link sap.ui.core.RenderManager Semantic Rendering API}.
 	 */
-	RenderManager.prototype.writeIcon = function(sURI, aClasses, mAttributes){
+	RenderManager.prototype.icon = function(sURI, aClasses, mAttributes){
 		var IconPool = sap.ui.require("sap/ui/core/IconPool");
 		if (!IconPool) {
 			Log.warning("Synchronous loading of IconPool due to sap.ui.core.RenderManager#icon call. " +
@@ -1992,6 +1970,30 @@ sap.ui.define([
 		return this;
 	};
 
+	/**
+	 * Writes either an &lt;img&gt; tag for normal URI or a &lt;span&gt; tag with needed properties for an icon URI.
+	 *
+	 * Additional classes and attributes can be added to the tag with the second and third parameter.
+	 * All of the given attributes are escaped for security consideration.
+	 *
+	 * When an &lt;img&gt; tag is rendered, the following two attributes are added by default
+	 * and can be overwritten with corresponding values in the <code>mAttributes</code> parameter:
+	 * <ul>
+	 * <li><code>role: "presentation"</code></Li>
+	 * <li><code>alt: ""</code></li>
+	 * </ul>
+	 *
+	 * @param {sap.ui.core.URI} sURI URI of an image or of an icon registered in {@link sap.ui.core.IconPool}
+	 * @param {array|string} [aClasses] Additional classes that are added to the rendered tag
+	 * @param {object} [mAttributes] Additional attributes that will be added to the rendered tag
+	 * @returns {this} Reference to <code>this</code> in order to allow method chaining
+	 * @public
+	 * @deprecated Since 1.92. Instead use {@link sap.ui.core.RenderManager#icon} of the {@link sap.ui.core.RenderManager Semantic Rendering API}.
+	 * @function
+	 */
+	RenderManager.prototype.writeIcon = RenderManager.prototype.icon;
+
+
 	/**
 	 * Returns the renderer class for a given control instance
 	 *

package/src/sap/ui/core/Renderer.js

@@ -19,7 +19,7 @@ sap.ui.define([
 	 * @classdesc Base Class for a Renderer.
 	 *
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 * @namespace
 	 * @public
 	 * @alias sap.ui.core.Renderer

package/src/sap/ui/core/ResizeHandler.js

@@ -33,7 +33,7 @@ sap.ui.define([
 	 * @alias sap.ui.core.ResizeHandler
 	 * @extends sap.ui.base.Object
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 * @public
 	 */
 

package/src/sap/ui/core/ScrollBar.js

@@ -44,7 +44,7 @@ sap.ui.define([
 	 * The ScrollBar control can be used for virtual scrolling of a certain area.
 	 * This means: to simulate a very large scrollable area when technically the area is small and the control takes care of displaying the respective part only. E.g. a Table control can take care of only rendering the currently visible rows and use this ScrollBar control to make the user think he actually scrolls through a long list.
 	 * @extends sap.ui.core.Control
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 *
 	 * @public
 	 * @deprecated as of version 1.56

package/src/sap/ui/core/SeparatorItem.js

@@ -23,7 +23,7 @@ sap.ui.define(['./Item', './library'],
 	 * @extends sap.ui.core.Item
 	 *
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 *
 	 * @public
 	 * @alias sap.ui.core.SeparatorItem

package/src/sap/ui/core/ShortcutHintsMixin.js

@@ -412,6 +412,10 @@ sap.ui.define([
 	oHintRegistry.mDOMNodes = {};
 
 	var oHintsEventDelegate = {
+		/**
+		 * @type {sap.ui.core.Control}
+		 * @private
+		 */
 		"onfocusin": function(oEvent) {
 			var oShortcutHintRefs = this._findShortcutOptionsForRef(oEvent.target);
 
@@ -424,6 +428,10 @@ sap.ui.define([
 			this._updateShortcutHintAccLabel(oShortcutHintRefs[0]);
 			this.showShortcutHint(oShortcutHintRefs);
 		},
+		/**
+		 * @type {sap.ui.core.Control}
+		 * @private
+		 */
 		"onfocusout": function(oEvent) {
 			var oShortcutHintRefs = this._findShortcutOptionsForRef(oEvent.target);
 
@@ -433,6 +441,10 @@ sap.ui.define([
 
 			this.hideShortcutHint();
 		},
+		/**
+		 * @type {sap.ui.core.Control}
+		 * @private
+		 */
 		"onmouseover": function(oEvent) {
 			var oShortcutHintRefs = this._findShortcutOptionsForRef(oEvent.target),
 				oDOMRef;
@@ -453,6 +465,10 @@ sap.ui.define([
 				this.showShortcutHint(oShortcutHintRefs);
 			}
 		},
+		/**
+		 * @type {sap.ui.core.Control}
+		 * @private
+		 */
 		"onmouseout": function(oEvent) {
 			var oShortcutHintRefs = this._findShortcutOptionsForRef(oEvent.target);
 
@@ -469,6 +485,10 @@ sap.ui.define([
 				this.hideShortcutHint();
 			}
 		},
+		/**
+		 * @type {sap.ui.core.Control}
+		 * @private
+		 */
 		"onAfterRendering": function() {
 			var aInfos = this.getRegisteredShortcutInfos(),
 				oElement,

package/src/sap/ui/core/Title.js

@@ -25,7 +25,7 @@ sap.ui.define(['./Element', './library'],
 	 * @extends sap.ui.core.Element
 	 *
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 *
 	 * @public
 	 * @since 1.16.0

package/src/sap/ui/core/TooltipBase.js

@@ -30,7 +30,7 @@ sap.ui.define([
 	 * @class
 	 * Abstract class that can be extended in order to implement any extended tooltip. For example, RichTooltip Control is based on it. It provides the opening/closing behavior and the main "text" property.
 	 * @extends sap.ui.core.Control
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 *
 	 * @public
 	 * @alias sap.ui.core.TooltipBase

package/src/sap/ui/core/UIArea.js

@@ -183,7 +183,7 @@ sap.ui.define([
 	 *
 	 * @extends sap.ui.base.ManagedObject
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 * @param {object} [oRootNode] reference to the DOM element that should be 'hosting' the UI Area.
 	 * @public
 	 * @alias sap.ui.core.UIArea
@@ -221,7 +221,7 @@ sap.ui.define([
 		},
 		metadata: {
 			// ---- object ----
-			publicMethods : ["setRootNode", "getRootNode", "setRootControl", "getRootControl", "lock","unlock", "isLocked", "_handleEvent"],
+			publicMethods : ["setRootNode", "getRootNode", "setRootControl", "getRootControl", "lock","unlock", "isLocked"],
 			aggregations : {
 				/**
 				 * Content that is displayed in the UIArea.
@@ -857,6 +857,7 @@ sap.ui.define([
 	 * registered event handlers.
 	 * @param {jQuery.Event} oEvent the jQuery event object
 	 * @private
+	 * @ui5-restricted sap.ui.core.dnd.DragAndDrop, sap.ui.core.FocusHandler
 	 */
 	UIArea.prototype._handleEvent = function(/**event*/oEvent) {
 		// execute the registered event handlers
@@ -1330,6 +1331,7 @@ sap.ui.define([
 	 * @returns {Element} the static, hidden area DOM element belonging to this core instance.
 	 * @throws {Error} an Error if the document is not yet ready
 	 * @private
+	 * @ui5-restricted sap.ui.core
 	 */
 	UIArea.getStaticAreaRef = function() {
 		if (!bDomReady) {

package/src/sap/ui/core/UIComponent.js

@@ -54,7 +54,7 @@ sap.ui.define([
 	 * @extends sap.ui.core.Component
 	 * @abstract
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 * @alias sap.ui.core.UIComponent
 	 * @since 1.9.2
 	 */

package/src/sap/ui/core/UIComponentMetadata.js

@@ -18,7 +18,7 @@ sap.ui.define(['./ComponentMetadata', 'sap/ui/core/mvc/ViewType'],
 	 * @experimental Since 1.15.1. The Component concept is still under construction, so some implementation details can be changed in future.
 	 * @class
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 * @since 1.15.1
 	 * @alias sap.ui.core.UIComponentMetadata
 	 * @extends sap.ui.core.ComponentMetadata

package/src/sap/ui/core/ValueStateSupport.js

@@ -16,7 +16,7 @@ sap.ui.define(['./Element', './library', "sap/base/assert"],
 		 * Helper functionality for value state support.
 		 *
 		 * @author SAP SE
-		 * @version 1.107.1
+		 * @version 1.108.1
 		 * @public
 		 * @namespace sap.ui.core.ValueStateSupport
 		 */

package/src/sap/ui/core/VariantLayoutData.js

@@ -20,7 +20,7 @@ sap.ui.define(['./LayoutData', './library'],
 	 * @class
 	 * Allows to add multiple LayoutData to one control in case that an easy switch of layouts (e.g. in a Form) is needed.
 	 * @extends sap.ui.core.LayoutData
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 *
 	 * @public
 	 * @since 1.9.2

package/src/sap/ui/core/XMLComposite.js

@@ -146,7 +146,7 @@ sap.ui.define([
 		 * @extends sap.ui.core.Control
 		 *
 		 * @author SAP SE
-		 * @version 1.107.1
+		 * @version 1.108.1
 		 * @since 1.56.0
 		 * @alias sap.ui.core.XMLComposite
 		 * @see {@link topic:b83a4dcb7d0e46969027345b8d32fd44 XML Composite Controls}

package/src/sap/ui/core/XMLCompositeMetadata.js

@@ -30,7 +30,7 @@ sap.ui.define([
 	 * @param {object} oClassInfo static info to construct the metadata from
 	 *
 	 * @author SAP SE
-	 * @version 1.107.1
+	 * @version 1.108.1
 	 * @since 1.50.0
 	 * @alias sap.ui.core.XMLCompositeMetadata
 	 * @extends sap.ui.core.ElementMetadata

package/src/sap/ui/core/_IconRegistry.js

@@ -561,13 +561,13 @@ sap.ui.define([
 				'sys-minus': 0xe1f7,
 				'dropdown': 0xe1f8,
 				'expand-group': 0xe1f9,
-				'collapse-group': 0xe200,
 				'vertical-grip': 0xe1fa,
 				'horizontal-grip': 0xe1fb,
 				'sort-descending': 0xe1fc,
 				'sort-ascending': 0xe1fd,
 				'arrow-down': 0xe1fe,
 				'legend': 0xe1ff,
+				'collapse-group': 0xe200,
 				'message-warning': 0xe201,
 				'message-information': 0x1e202,
 				'message-success': 0x1e203,
@@ -714,21 +714,25 @@ sap.ui.define([
 				'space-navigation': 0xe290,
 				'in-progress': 0x1e291,
 				'not-editable': 0xe292,
+				'heart': 0xe293,
+				'heart-2': 0xe294,
+				'tri-state': 0xe295,
 				'bookmark-2': 0xe296,
 				'detail-less': 0xe297,
 				'detail-more': 0xe298,
 				'flag-2': 0x1e299,
 				'folder-2': 0xe29a,
-				'heart': 0xe293,
-				'heart-2': 0xe294,
 				'paint-bucket': 0xe29b,
-				'tri-state': 0xe295,
-				'non-binary': 0xe29d,
 				'direction-arrows': 0xe29c,
+				'non-binary': 0xe29d,
 				'female': 0xe29e,
-				'gender-male-and-female': 0x1e300,
 				'male': 0x1e29f,
-				'rotate': 0xe301
+				'gender-male-and-female': 0x1e300,
+				'rotate': 0xe301,
+				'locate-me-2': 0xe302,
+				'map-fill': 0xe303,
+				'cloud-check': 0x1e304,
+				'enablement': 0x1e305
 			}
 		};