@sapui5/ts-types-esm 1.140.0 → 1.141.0

package/types/sap.ui.dt.d.ts

@@ -1,4 +1,205 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
+
+declare module "sap/ui/dt/library" {
+  export namespace designtime {
+    namespace DesignTimeMetadata {
+      /**
+       * Object containing the aggregation configuration
+       */
+      type Aggregation = {
+        /**
+         * Used to ignore the aggregation (and all its children) at design time. For example, this can be used to
+         * ignore deprecated or duplicated aggregations as well as aggregations irrelevant during the design time
+         * (such as dependents). If the value is true, then no overlays will be created for the aggregation and
+         * its children. For more options on how to disable actions in design time please refer to the UI5 Demo
+         * Kit.
+         */
+        ignore?: boolean | Function;
+        /**
+         * Defines the DOM reference of the aggregation. The DOM reference is used to calculate the dimension of
+         * the aggregation at design time. This is needed, for instance, to make drag&drop possible. If no domRef
+         * property is given, a heuristic is used to calculate the dimension of the aggregation from its children
+         * during the design time.
+         */
+        domRef?: string | Function;
+        /**
+         * Provide or compute name for the controls inside the aggregation which is understandable for the key user.
+         * This is needed for the "addODataProperty" and "createContainer" action to show the names in the context
+         * menu (Add , Available ). Name the control based on the general UI concept and follow
+         * the guidance from https://experience.sap.com/fiori-design/. The key user doesn't care about the difference
+         * between a smart, mobile, or responsive version of a form, it's just a form.
+         */
+        childNames?:
+          | {
+              /**
+               * i18n key from library's design-time resource bundle or function returning the translated text
+               */
+              singular: string | Function;
+              /**
+               * i18n key from library's design-time resource bundle or function returning the translated text
+               */
+              plural: string | Function;
+            }
+          | Function;
+        /**
+         * Actions that can be performed on the aggregation (e.g. move).
+         */
+        actions?: object;
+        /**
+         * Returns DesignTime-Metadata object which extends or overrides existing metadata of a successor control.
+         * In the negative case it returns the boolean "false" value. The propagateMetadata function gets 2 parameters
+         * passed through during execution: oControl and oRelevantContainerControl. The second parameter is the
+         * control which has defined this propagation function. It can be used if you need to know the relevantContainer
+         * during the execution of the function.
+         */
+        propagateMetadata?: Function;
+        /**
+         * Defines the relevant container control for the actions which belong to successor controls.
+         */
+        propagateRelevantContainer?: boolean | Function;
+      };
+
+      /**
+       * Object containing the association configuration
+       */
+      type Association = {
+        /**
+         * Can be used to tell the design time that it should follow the association hierarchy. This is used by
+         * controls like e.g. the componentContainer that should allow to follow the association component, which
+         * defines the control hierarchy but is not a real aggregation (more isolation, regarding model propagation/rendering/eventing/...).
+         */
+        aggregationLike: boolean;
+      };
+
+      /**
+       * Object containing the aggregation configuration
+       */
+      type Property = {
+        /**
+         * Used to ignore the property at design time. For example, this can be used to ignore deprecated properties
+         * or properties that shall not be changed during design time.
+         */
+        ignore?: boolean | Function;
+      };
+    }
+
+    /**
+     * Object containing a sample design time configuration
+     */
+    type DesignTimeMetadata = {
+      /**
+       * Specify or calculate a speaking name for the control (which is understandable to key users). This is
+       * needed for the "reveal" action to show the names in the context menu (Add  and Available
+       * ). Name your control based on the general UI concept and follow the guidance from https://experience.sap.com/fiori-design/.
+       * Example: Key users don't care about the difference between a smart, mobile or responsive version of a
+       * form, it's just a form.
+       */
+      name:
+        | {
+            /**
+             * i18n key from library's design-time resource bundle or function returning the translated text
+             */
+            singular: string | Function;
+            /**
+             * i18n key from library's design-time resource bundle or function returning the translated text
+             */
+            plural: string | Function;
+          }
+        | Function;
+      /**
+       * Allows to provide a customized getter for the control label that is used in outlines, context menus and
+       * actions like "reveal" or "rename". The default implementation tries to get the following properties in
+       * that order: `text`, `labelText`, `label`, `title`, `heading`, `dataSourceLabel`
+       */
+      getLabel?: Function;
+      /**
+       * Defines the DOM reference of the control
+       */
+      domRef?: string | Function;
+      /**
+       * Needed for Elements that are not derived from sap.ui.core.Control. The function should return the visibility
+       * of the Element as a boolean (true = visible). This function can be called before the DOM is ready.
+       */
+      isVisible: Function;
+      /**
+       * Palette settings for the control.
+       */
+      palette:
+        | {
+            /**
+             * Possible values: "ACTION", "DISPLAY", "LAYOUT", "LIST", "INPUT", "CONTAINER", "CHART", "TILE"
+             */
+            group: string | Function;
+            /**
+             * Preferable as SVG as this icon scales
+             */
+            icon: string | Function;
+          }
+        | Function;
+      /**
+       * Create template will not be inherited, they are special to the current type.
+       */
+      templates: {
+        /**
+         * Path to the template file
+         */
+        create: string;
+      };
+      /**
+       * RTA specific actions that can be performed on the control.
+       */
+      actions: object;
+      /**
+       * Configuration for the properties of the control. See sap.ui.dt.DesignTimeMetadata.Property
+       */
+      properties: object;
+      /**
+       * Configuration for the aggregations of the control. See sap.ui.dt.DesignTimeMetadata.Aggregation
+       */
+      aggregations: object;
+      /**
+       * Describes the associations of the control. Per default no association is followed as overlays should
+       * match the control hierarchy. No actions are supported for associations. See sap.ui.dt.DesignTimeMetadata.Association
+       */
+      associations: object;
+      /**
+       * Describes the OData annotations that are actively used by your control. This section needs to be filled
+       * for controls evaluating annotations. It can be used for documentation purposes, but is also evaluated
+       * by UI adaptation at design time.
+       */
+      annotations: object;
+      /**
+       * Describes the scroll containers of the control. This is needed when there are more than one aggregation
+       * in one scroll container (e.g. ObjectPageLayout: Header + Sections).
+       */
+      scrollContainers: Array<{
+        /**
+         * Defines the DOM reference for the scroll wrapper
+         */
+        domRef: string | Function;
+        /**
+         * Names of the aggregations inside the scroll wrapper. Two arguments are passed to the function: the control
+         * instance and an update function that can be called if the aggregations change.
+         */
+        aggregations: string[] | Function;
+      }>;
+      /**
+       * This object defines hooks that are being called when a tool, e.g. Runtime Adaptation, is started and
+       * stopped. The functions are being called with the control instance as parameter.
+       */
+      tool: {
+        /**
+         * Called when the tool is started
+         */
+        start: Function;
+        /**
+         * Called when the tool is stopped
+         */
+        stop: Function;
+      };
+    };
+  }
+}
 
 declare namespace sap {
   interface IUI5DefineDependencyNames {

package/types/sap.ui.export.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
 
 declare module "sap/ui/export/library" {
   import ListBinding from "sap/ui/model/ListBinding";

package/types/sap.ui.fl.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
 
 declare module "sap/ui/fl/library" {}
 
@@ -12,10 +12,11 @@ declare module "sap/ui/fl/apply/api/ControlVariantApplyAPI" {
    */
   interface ControlVariantApplyAPI {
     /**
-     * Activates the passed variant applicable to the passed control/component. If the Variant is not available
-     * and the backend supports lazy loading, a backend request is made to fetch the variant. If the flag standardVariant
-     * is set to true, the standard variant is activated and the variantReference is ignored. In this scenario
-     * the passed element must be the variant management control.
+     * Activates the passed variant applicable to the passed control/component. The corresponding variant management
+     * control must be available when this function is called. If the variant is not found and the backend supports
+     * lazy loading, a backend request is made to fetch the variant. If the flag standardVariant is set to true,
+     * the standard variant is activated and the variantReference is ignored: in this scenario, the passed element
+     * must be the variant management control.
      *
      *
      * @returns Resolves after the variant is activated or rejects if an error occurs
@@ -1621,8 +1622,6 @@ declare namespace sap {
 
     "sap/ui/fl/apply/_internal/preprocessors/ComponentLifecycleHooks": undefined;
 
-    "sap/ui/fl/apply/_internal/preprocessors/ControllerExtension": undefined;
-
     "sap/ui/fl/apply/api/AnnotationChangeHandlerAPI": undefined;
 
     "sap/ui/fl/apply/api/ControlVariantApplyAPI": undefined;
@@ -1667,6 +1666,8 @@ declare namespace sap {
 
     "sap/ui/fl/initial/_internal/connectors/Utils": undefined;
 
+    "sap/ui/fl/initial/_internal/preprocessors/ControllerExtension": undefined;
+
     "sap/ui/fl/initial/_internal/Settings": undefined;
 
     "sap/ui/fl/initial/_internal/Storage": undefined;

package/types/sap.ui.generic.app.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
 
 declare module "sap/ui/generic/app/library" {
   export namespace navigation {

package/types/sap.ui.generic.template.d.ts

@@ -1,3 +1,3 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
 
 declare namespace sap {}

package/types/sap.ui.integration.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
 
 declare module "sap/ui/integration/library" {
   import { URI } from "sap/ui/core/library";

package/types/sap.ui.layout.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
 
 declare module "sap/ui/layout/library" {
   import Control from "sap/ui/core/Control";
@@ -6516,23 +6516,27 @@ declare module "sap/ui/layout/form/Form" {
    * A `Form` control arranges labels and fields (like input fields) into groups and rows. There are different
    * ways to visualize forms for different screen sizes.
    *
-   * A `Form` is structured into `FormContainers`. Each `FormContainer` consists of `FormElements`. The `FormElements`
-   * consists of a label and the form fields. A `Form` doesn't render its content by itself. The rendering
-   * is done by the assigned `FormLayout`. This is so that the rendering can be adopted to new UI requirements
-   * without changing the `Form` itself.
+   * A `Form` is structured into `FormContainers`. Each {@link sap.ui.layout.form.FormContainer FormContainer }
+   * consists of `FormElements`. The {@link sap.ui.layout.form.FormElement FormElement} consists of a label
+   * and the form fields. A `Form` doesn't render its content on its own. The rendering is done by the assigned
+   * {@link sap.ui.layout.form.FormLayout FormLayout}. This is so that the rendering can be adopted to new
+   * UI requirements without changing the `Form` itself.
    *
-   * For the content of a `Form`, `VariantLayoutData` are supported to allow simple switching of the `FormLayout`.
-   * `LayoutData` on the content can be used to overwrite the default layout of the `Form`.
+   * For the content of a `Form`, {@link sap.ui.core.VariantLayoutData VariantLayoutData} are supported to
+   * allow simple switching of the `FormLayout`. `LayoutData` on the content can be used to overwrite the
+   * default layout of the `Form`.
    *
    * The `Form` (and its sub-controls) automatically add label and field assignment to enable screen reader
    * support. It also adds keyboard support to navigate between the fields and groups inside the form.
    *
-   * **Warning:** Do not put any layout or other container controls into the `FormElement`. Views are also
-   * not supported. This could damage the visual layout, keyboard support and screen-reader support.
+   * **Warning:** Do not put any layout or other container controls into the {@link sap.ui.layout.form.FormElement FormElement}.
+   * Views are also not supported. This could damage the visual layout, keyboard support and screen-reader
+   * support.
    *
    * If editable controls are used as content, the `editable` property must be set to `true`, otherwise to
    * `false`. If the `editable` property is set incorrectly, there will be visual issues like wrong label
-   * alignment or wrong spacing between the controls.
+   * alignment or wrong spacing between the controls. In addition to that, wrong screen reader announcements
+   * might occur.
    *
    * @since 1.16.0
    */
@@ -6673,7 +6677,8 @@ declare module "sap/ui/layout/form/Form" {
      *
      * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
      * might be misaligned, the labels might be rendered in the wrong mode, and the spacing between the single
-     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly.
+     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly. In addition
+     * to that, wrong screen reader announcements might occur.
      *
      * Default value is `false`.
      *
@@ -6817,7 +6822,8 @@ declare module "sap/ui/layout/form/Form" {
      *
      * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
      * might be misaligned, the labels might be rendered in the wrong mode, and the spacing between the single
-     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly.
+     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly. In addition
+     * to that, wrong screen reader announcements might occur.
      *
      * When called with a value of `null` or `undefined`, the default value of the property will be restored.
      *
@@ -6908,7 +6914,8 @@ declare module "sap/ui/layout/form/Form" {
      *
      * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
      * might be misaligned, the labels might be rendered in the wrong mode, and the spacing between the single
-     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly.
+     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly. In addition
+     * to that, wrong screen reader announcements might occur.
      *
      * @since 1.20.0
      */
@@ -9528,7 +9535,7 @@ declare module "sap/ui/layout/form/SimpleForm" {
    * a `{@link sap.ui.layout.form.Form Form}` control is created along with its `{@link sap.ui.layout.form.FormContainer FormContainer}`
    * elements and `{@link sap.ui.layout.form.FormElement FormElement}` elements, but the complexity in the
    * API is not exposed to the user.
-   * 	 - A new `sap.ui.core.Title` element or `Toolbar` control starts a new group (`{@link sap.ui.layout.form.FormContainer FormContainer}`)
+   * 	 - A new {@link sap.ui.core.Title Title} element or `Toolbar` control starts a new group (`{@link sap.ui.layout.form.FormContainer FormContainer}`)
    *     in the form.
    * 	 - A new `Label` control starts a new row (`{@link sap.ui.layout.form.FormElement FormElement}`) in
    *     the form.
@@ -9784,7 +9791,7 @@ declare module "sap/ui/layout/form/SimpleForm" {
      * Gets content of aggregation {@link #getContent content}.
      *
      * The content of the form is structured in the following way:
-     * 	 - Add a `sap.ui.core.Title` element or `Toolbar` control to start a new group (`{@link sap.ui.layout.form.FormContainer FormContainer}`).
+     * 	 - Add a {@link sap.ui.core.Title Title} element or `Toolbar` control to start a new group (`{@link sap.ui.layout.form.FormContainer FormContainer}`).
      *
      * 	 - Add a `Label` control to start a new row (`{@link sap.ui.layout.form.FormElement FormElement}`).
      *
@@ -9792,26 +9799,28 @@ declare module "sap/ui/layout/form/SimpleForm" {
      * 	 - Use `LayoutData` to influence the layout for special cases in the single controls. For example, if
      *     a `ColumnLayout` is used as a layout, the form content is weighted using 4 cells for the labels and 8
      *     cells for the field part, for large size. If there is only little space, the labels are above the fields
-     *     and each field uses 12 cells. If your input controls should influence their width, you can add `sap.ui.layout.ColumnElementData`
-     *     to them via `setLayoutData` method. Ensure that the sum of the weights in the `ColumnElementData` is
-     *     not more than 12, as this is the total width of the input control part of each form row.  Example
-     *     for a row where the `Input` uses 6 cells and the second `Input` uses 2 cells (using `ColumnElementData`):
+     *     and each field uses 12 cells. If your input controls should influence their width, you can add {@link sap.ui.layout.form.ColumnElementData ColumnElementData }
+     *     to them via the {@link #setLayoutData setLayoutData} method. Ensure that the sum of the weights in the
+     *     {@link sap.ui.layout.form.ColumnElementData ColumnElementData} is not more than 12, as this is the total
+     *     width of the input control part of each form row.  Example for a row where the {@link sap.m.Input Input }
+     *     uses 6 cells and the second {@link sap.m.Input Input} uses 2 cells (using {@link sap.ui.layout.form.ColumnElementData ColumnElementData}):
      *
      * ```javascript
      *
      * new sap.m.Label({text:"Label"});
-     * new sap.m.Input({value:"6 cells", layoutData: new sap.ui.layout.ColumnElementData({cellsLarge: 6, cellsSmall: 8})}),
-     * new sap.m.Input({value:"2 cells", layoutData: new sap.ui.layout.ColumnElementData({cellsLarge: 2, cellsSmall: 4})}),
+     * new sap.m.Input({value:"6 cells", layoutData: new sap.ui.layout.form.ColumnElementData({cellsLarge: 6, cellsSmall: 8})}),
+     * new sap.m.Input({value:"2 cells", layoutData: new sap.ui.layout.form.ColumnElementData({cellsLarge: 2, cellsSmall: 4})}),
      * ```
      *
      *
-     * For example, if a `ResponsiveGridLayout` is used as a layout, there are 12 cells in one row. Depending
-     * on the screen size the labels use the defined `labelSpan`. The remaining cells are used for the fields
-     * (and `emptySpan` if defined). The available cells are distributed to all fields in the row. If one field
-     * should use a fixed number of cells you can add `sap.ui.layout.GridData` to them via `setLayoutData` method.
-     * If there are additional fields in the row they will get the remaining cells.  Example for a row
-     * with two `Input` controls where one uses four cells on small screens, one cell on medium screens and
-     * 2 cells on larger screens (using `ResponsiveGridLayout`):
+     * For example, if a {@link sap.ui.layout.ResponsiveGridLayout ResponsiveGridLayout} is used as a layout,
+     * there are 12 cells in one row. Depending on the screen size the labels use the defined `labelSpan`. The
+     * remaining cells are used for the fields (and `emptySpan` if defined). The available cells are distributed
+     * to all fields in the row. If one field should use a fixed number of cells you can add {@link sap.ui.layout.GridData GridData }
+     * to them via the {@link #setLayoutData setLayoutData} method. If there are additional fields in the row
+     * they will get the remaining cells.  Example for a row with two {@link sap.m.Input Input} controls
+     * where one uses four cells on small screens, one cell on medium screens and 2 cells on larger screens
+     * (using {@link sap.ui.layout.ResponsiveGridLayout ResponsiveGridLayout}):
      * ```javascript
      *
      * new sap.m.Label({text:"Label"});
@@ -9826,7 +9835,8 @@ declare module "sap/ui/layout/form/SimpleForm" {
      *
      * If editable controls are used as content, the `editable` property must be set to `true`, otherwise to
      * `false`. If the `editable` property is set incorrectly, there will be visual issues like wrong label
-     * alignment or wrong spacing between the controls.
+     * alignment or wrong spacing between the controls. In addition to that, wrong screen reader announcements
+     * might occur.
      */
     getContent(): UI5Element[];
     /**
@@ -9843,7 +9853,8 @@ declare module "sap/ui/layout/form/SimpleForm" {
      *
      * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
      * might be misaligned, the labels might be rendered in the wrong mode, and the spacing between the single
-     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly.
+     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly. In addition
+     * to that, wrong screen reader announcements might occur.
      *
      * Default value is `false`.
      *
@@ -10364,7 +10375,8 @@ declare module "sap/ui/layout/form/SimpleForm" {
      *
      * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
      * might be misaligned, the labels might be rendered in the wrong mode, and the spacing between the single
-     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly.
+     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly. In addition
+     * to that, wrong screen reader announcements might occur.
      *
      * When called with a value of `null` or `undefined`, the default value of the property will be restored.
      *
@@ -10771,7 +10783,8 @@ declare module "sap/ui/layout/form/SimpleForm" {
      *
      * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
      * might be misaligned, the labels might be rendered in the wrong mode, and the spacing between the single
-     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly.
+     * controls might be wrong. Also, controls that do not fit the mode might be rendered incorrectly. In addition
+     * to that, wrong screen reader announcements might occur.
      */
     editable?: boolean | PropertyBindingInfo | `{${string}}`;
 
@@ -10987,7 +11000,7 @@ declare module "sap/ui/layout/form/SimpleForm" {
 
     /**
      * The content of the form is structured in the following way:
-     * 	 - Add a `sap.ui.core.Title` element or `Toolbar` control to start a new group (`{@link sap.ui.layout.form.FormContainer FormContainer}`).
+     * 	 - Add a {@link sap.ui.core.Title Title} element or `Toolbar` control to start a new group (`{@link sap.ui.layout.form.FormContainer FormContainer}`).
      *
      * 	 - Add a `Label` control to start a new row (`{@link sap.ui.layout.form.FormElement FormElement}`).
      *
@@ -10995,26 +11008,28 @@ declare module "sap/ui/layout/form/SimpleForm" {
      * 	 - Use `LayoutData` to influence the layout for special cases in the single controls. For example, if
      *     a `ColumnLayout` is used as a layout, the form content is weighted using 4 cells for the labels and 8
      *     cells for the field part, for large size. If there is only little space, the labels are above the fields
-     *     and each field uses 12 cells. If your input controls should influence their width, you can add `sap.ui.layout.ColumnElementData`
-     *     to them via `setLayoutData` method. Ensure that the sum of the weights in the `ColumnElementData` is
-     *     not more than 12, as this is the total width of the input control part of each form row.  Example
-     *     for a row where the `Input` uses 6 cells and the second `Input` uses 2 cells (using `ColumnElementData`):
+     *     and each field uses 12 cells. If your input controls should influence their width, you can add {@link sap.ui.layout.form.ColumnElementData ColumnElementData }
+     *     to them via the {@link #setLayoutData setLayoutData} method. Ensure that the sum of the weights in the
+     *     {@link sap.ui.layout.form.ColumnElementData ColumnElementData} is not more than 12, as this is the total
+     *     width of the input control part of each form row.  Example for a row where the {@link sap.m.Input Input }
+     *     uses 6 cells and the second {@link sap.m.Input Input} uses 2 cells (using {@link sap.ui.layout.form.ColumnElementData ColumnElementData}):
      *
      * ```javascript
      *
      * new sap.m.Label({text:"Label"});
-     * new sap.m.Input({value:"6 cells", layoutData: new sap.ui.layout.ColumnElementData({cellsLarge: 6, cellsSmall: 8})}),
-     * new sap.m.Input({value:"2 cells", layoutData: new sap.ui.layout.ColumnElementData({cellsLarge: 2, cellsSmall: 4})}),
+     * new sap.m.Input({value:"6 cells", layoutData: new sap.ui.layout.form.ColumnElementData({cellsLarge: 6, cellsSmall: 8})}),
+     * new sap.m.Input({value:"2 cells", layoutData: new sap.ui.layout.form.ColumnElementData({cellsLarge: 2, cellsSmall: 4})}),
      * ```
      *
      *
-     * For example, if a `ResponsiveGridLayout` is used as a layout, there are 12 cells in one row. Depending
-     * on the screen size the labels use the defined `labelSpan`. The remaining cells are used for the fields
-     * (and `emptySpan` if defined). The available cells are distributed to all fields in the row. If one field
-     * should use a fixed number of cells you can add `sap.ui.layout.GridData` to them via `setLayoutData` method.
-     * If there are additional fields in the row they will get the remaining cells.  Example for a row
-     * with two `Input` controls where one uses four cells on small screens, one cell on medium screens and
-     * 2 cells on larger screens (using `ResponsiveGridLayout`):
+     * For example, if a {@link sap.ui.layout.ResponsiveGridLayout ResponsiveGridLayout} is used as a layout,
+     * there are 12 cells in one row. Depending on the screen size the labels use the defined `labelSpan`. The
+     * remaining cells are used for the fields (and `emptySpan` if defined). The available cells are distributed
+     * to all fields in the row. If one field should use a fixed number of cells you can add {@link sap.ui.layout.GridData GridData }
+     * to them via the {@link #setLayoutData setLayoutData} method. If there are additional fields in the row
+     * they will get the remaining cells.  Example for a row with two {@link sap.m.Input Input} controls
+     * where one uses four cells on small screens, one cell on medium screens and 2 cells on larger screens
+     * (using {@link sap.ui.layout.ResponsiveGridLayout ResponsiveGridLayout}):
      * ```javascript
      *
      * new sap.m.Label({text:"Label"});
@@ -11029,7 +11044,8 @@ declare module "sap/ui/layout/form/SimpleForm" {
      *
      * If editable controls are used as content, the `editable` property must be set to `true`, otherwise to
      * `false`. If the `editable` property is set incorrectly, there will be visual issues like wrong label
-     * alignment or wrong spacing between the controls.
+     * alignment or wrong spacing between the controls. In addition to that, wrong screen reader announcements
+     * might occur.
      */
     content?:
       | UI5Element[]

package/types/sap.ui.mdc.d.ts

@@ -1,4 +1,4 @@
-// For Library Version: 1.140.0
+// For Library Version: 1.141.0
 
 declare module "sap/ui/mdc/AggregationBaseDelegate" {
   import BaseDelegate from "sap/ui/mdc/BaseDelegate";
@@ -1953,9 +1953,9 @@ declare module "sap/ui/mdc/odata/v4/TableDelegate" {
      * If an update is not possible, it rebinds the table.
      *
      * Compares the current and previous state of the table to detect whether rebinding is necessary. The diffing
-     * is done for the sorters, filters, aggregation, parameters. Other {@link sap.ui.base.ManagedObject.AggregationBindingInfo binding info }
-     * keys, such as `path`, `events`, or `model`, must be provided in `updateBindingInfo`, and those keys must
-     * not be changed conditionally.
+     * is done for the sorters, filters, aggregation, parameters, and the path of the binding. Other {@link sap.ui.base.ManagedObject.AggregationBindingInfo binding info }
+     * keys, such as `events` or `model`, must be provided in `updateBindingInfo`, and those keys must not be
+     * changed conditionally.
      *
      * **Note:** To remove a binding info parameter, the value must be set to `undefined` in `updateBindingInfo`.
      * For more information, see {@link sap.ui.model.odata.v4.ODataListBinding#changeParameters}.