@sapui5/ts-types 1.141.2 → 1.142.0

package/types/{dt-1.141.0-d.ts → sap.ui.dt.d.ts}

@@ -1,4 +1,4 @@
-// For Library Version: 1.141.0
+// For Library Version: 1.142.0
 
 declare namespace sap {
   interface IUI5DefineDependencyNames {

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.141.1
+// For Library Version: 1.142.0
 
 declare namespace sap {
   namespace ui {
@@ -192,6 +192,59 @@ declare namespace sap {
        */
       interface Spreadsheet$BeforeSaveEventParameters {}
 
+      /**
+       * @since 1.142
+       */
+      class CommaSeparatedValues extends sap.ui.export.ExportBase {
+        /**
+         * Provides functionality to export data in CSV format.
+         *
+         * The `CommaSeparatedValues` class extends the `ExportBase` class and provides the functionality to create
+         * CSV files. It supports appending data, validating data, escaping content, and building the final CSV
+         * file. Additionally, it provides methods to process data sources, apply default export settings, and manage
+         * the export process.
+         *
+         * There are the following key features:
+         * 	 - Supports JSON arrays and ClientListBindings as data sources.
+         * 	 - Escapes special characters and prevents CSV injection.
+         * 	 - Adds a UTF-8 Byte Order Mark (BOM) for compatibility with spreadsheet software.
+         *
+         * Example Usage: ```javascript const oCSV = new sap.ui.export.CommaSeparatedValues(mSettings); oCSV.build(); ```
+         */
+        constructor();
+
+        /**
+         * Creates a new subclass of class sap.ui.export.CommaSeparatedValues with name `sClassName` and enriches
+         * it with the information contained in `oClassInfo`.
+         *
+         * `oClassInfo` might contain the same kind of information as described in {@link sap.ui.export.ExportBase.extend}.
+         *
+         *
+         * @returns Created class / constructor function
+         */
+        static extend<T extends Record<string, unknown>>(
+          /**
+           * Name of the class being created
+           */
+          sClassName: string,
+          /**
+           * Object literal with information about the class
+           */
+          oClassInfo?: sap.ClassInfo<T, sap.ui.export.CommaSeparatedValues>,
+          /**
+           * Constructor function for the metadata object; if not given, it defaults to the metadata implementation
+           * used by this class
+           */
+          FNMetaImpl?: Function
+        ): Function;
+        /**
+         * Returns a metadata object for class sap.ui.export.CommaSeparatedValues.
+         *
+         *
+         * @returns Metadata object describing this class
+         */
+        static getMetadata(): sap.ui.base.Metadata;
+      }
       /**
        * The `sap.ui.export.ExportBase` class allows you to export table data from a UI5 application to certain
        * formats. This class is an abstract class that requires specific implementations for each file format.
@@ -1111,6 +1164,8 @@ declare namespace sap {
   }
 
   interface IUI5DefineDependencyNames {
+    "sap/ui/export/CommaSeparatedValues": undefined;
+
     "sap/ui/export/ExportBase": undefined;
 
     "sap/ui/export/ExportHandler": undefined;

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.141.1
+// For Library Version: 1.142.0
 
 declare namespace sap {
   namespace ui {

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.141.0
+// For Library Version: 1.142.0
 
 declare namespace sap {
   namespace ui {

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

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

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.141.1
+// For Library Version: 1.142.0
 
 declare namespace sap {
   namespace ui {

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.141.1
+// For Library Version: 1.142.0
 
 declare namespace sap {
   namespace ui {
@@ -165,7 +165,7 @@ declare namespace sap {
            *
            * The labels inside the form will be rendered by default in the according mode.
            *
-           * **Note:** The setting of this property does not change the content of the form. For example, `Input`
+           * **Note:** The setting of this property does not change the content of the form. For example, {@link sap.m.Input Input }
            * controls in a form with `editable` set to false are still editable.
            *
            * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
@@ -193,7 +193,7 @@ declare namespace sap {
            * Title of the `Form`. Can either be a `Title` element or a string. If a `Title` element it used, the style
            * of the title can be set.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored.
+           * **Note:** If a {@link #getToolbar Toolbar} is used, the `Title` is ignored.
            *
            * **Note:** If the title is provided as a string, the title is rendered with a theme-dependent default
            * level. As the `Form` control cannot know the structure of the page, this might not fit the page structure.
@@ -208,9 +208,9 @@ declare namespace sap {
           /**
            * Toolbar of the `Form`.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored. If a title is needed inside the `Toolbar` it
-           * must be added at content to the `Toolbar`. In this case, add the `Title` to the `ariaLabelledBy` association.
-           * Use the right title level to meet the visual requirements. This might be theme-dependent.
+           * **Note:** If a `Toolbar` is used, the {@link #getTitle Title} is ignored. If a title is needed inside
+           * the `Toolbar` it must be added at content to the `Toolbar`. In this case, add the `Title` to the {@link #addAriaLabelledBy ariaLabelledBy }
+           * association. Use the right title level to meet the visual requirements. This might be theme-dependent.
            *
            * @since 1.36.0
            */
@@ -226,7 +226,7 @@ declare namespace sap {
            * Association to controls / IDs that label this control (see WAI-ARIA attribute `aria-labelledby`).
            *
            * **Note:** Every `Form` needs to have some title or label (at least for screen reader support). If no
-           * `Title` is set, and the `Form` is not a child or a control with a title, such as {@link sap.m.Panel Panel }
+           * {@link #getTitle Title} is set, and the `Form` is not a child or a control with a title, such as {@link sap.m.Panel Panel }
            * or {@link sap.m.Dialog Dialog}, a label or title needs to be assigned using the `ariaLabelledBy` association.
            *
            * @since 1.28.0
@@ -241,7 +241,7 @@ declare namespace sap {
           /**
            * Container is expanded.
            *
-           * **Note:** This property only works if `expandable` is set to `true`.
+           * **Note:** This property only works if {@link #getExpandable expandable} is set to `true`.
            */
           expanded?:
             | boolean
@@ -251,7 +251,7 @@ declare namespace sap {
           /**
            * Defines if the `FormContainer` is expandable.
            *
-           * **Note:** The expander icon will only be shown if a `title` is set for the `FormContainer`.
+           * **Note:** The expander icon will only be shown if a {@link #getTitle Title} is set for the `FormContainer`.
            */
           expandable?:
             | boolean
@@ -279,7 +279,7 @@ declare namespace sap {
            * Title of the `FormContainer`. Can either be a `Title` element or a string. If a `Title` element is used,
            * the style of the title can be set.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored.
+           * **Note:** If a {@link #getToolbar Toolbar} is used, the `Title` is ignored.
            *
            * **Note:** If the title is provided as a string, the title is rendered with a theme-dependent default
            * level. As the `Form` control cannot know the structure of the page, this might not fit the page structure.
@@ -294,9 +294,9 @@ declare namespace sap {
           /**
            * Toolbar of the `FormContainer`.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored. If a title is needed inside the `Toolbar` it
-           * must be added at content to the `Toolbar`. In this case add the `Title` to the `ariaLabelledBy` association.
-           * Use the right title level to meet the visual requirements. This might be theme-dependent.
+           * **Note:** If a `Toolbar` is used, the {@link #getTitle Title} is ignored. If a title is needed inside
+           * the `Toolbar` it must be added at content to the `Toolbar`. In this case add the `Title` to the {@link #addAriaLabelledBy ariaLabelledBy }
+           * association. Use the right title level to meet the visual requirements. This might be theme-dependent.
            *
            * @since 1.36.0
            */
@@ -309,8 +309,8 @@ declare namespace sap {
            * used `FormLayout`.
            *
            * **Note:** If there is more than one `FormContainers`, every `FormContainer` needs to have some title
-           * or label (at least for screen reader support). If no `Title` is set, a label or title needs to be assigned
-           * using the `ariaLabelledBy` association.
+           * or label (at least for screen reader support). If no {@link #getTitle Title} is set, a label or title
+           * needs to be assigned using the `ariaLabelledBy` association.
            *
            * @since 1.36.0
            */
@@ -345,7 +345,7 @@ declare namespace sap {
            *
            * **Warning:** Do not put any layout or other container controls in here. This could damage the visual
            * layout, keyboard support and screen-reader support. Only form controls are allowed. Views are also not
-           * supported. Allowed controls implement the interface `sap.ui.core.IFormContent`.
+           * supported. Allowed controls implement the interface {@link sap.ui.core.IFormContent}.
            */
           fields?:
             | sap.ui.core.Control[]
@@ -1009,18 +1009,19 @@ declare namespace sap {
            * The content of the form is structured in the following way:
            * 	 - 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}`).
+           * 	 - Add a {@link sap.m.Label Label} control to start a new row (`{@link sap.ui.layout.form.FormElement FormElement}`).
            *
            * 	 - Add controls as input fields, text fields or other as needed.
-           * 	 - 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 {@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}):
-           *
+           * 	 - Use {@link sap.ui.core.Element#setLayoutData LayoutData} to influence the layout for special cases
+           *     in the single controls. For example, if a {@link sap.ui.layout.ColumnLayout 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 {@link sap.ui.layout.form.ColumnElementData ColumnElementData }
+           *     to them via the {@link sap.ui.core.Element#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"});
@@ -1033,10 +1034,10 @@ declare namespace sap {
            * 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}):
+           * to them via the {@link sap.ui.core.Element#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"});
@@ -1047,12 +1048,12 @@ declare namespace sap {
            *
            * **Warning:** Do not put any layout or other container controls in here. This could damage the visual
            * layout, keyboard support and screen-reader support. Only labels, titles, toolbars and form controls are
-           * allowed. Views are also not supported. Allowed form controls implement the interface `sap.ui.core.IFormContent`.
+           * allowed. Views are also not supported. Allowed form controls implement the interface {@link sap.ui.core.IFormContent}.
            *
-           * 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. In addition to that, wrong screen reader announcements
-           * might occur.
+           * If editable controls are used as content, the {@link #setEditable editable} property must be set to `true`,
+           * otherwise to `false`. If the {@link #setEditable editable} property is set incorrectly, there will be
+           * visual issues like wrong label alignment or wrong spacing between the controls. In addition to that,
+           * wrong screen reader announcements might occur.
            */
           content?:
             | sap.ui.core.Element[]
@@ -1063,7 +1064,7 @@ declare namespace sap {
           /**
            * Title element of the `SimpleForm`. Can either be a `Title` element, or a string.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored.
+           * **Note:** If a {@link #getToolbar Toolbar} is used, the `Title` is ignored.
            *
            * **Note:** If the title is provided as a string, the title is rendered with a theme-dependent default
            * level. As the `Form` control cannot know the structure of the page, this might not fit the page structure.
@@ -1080,8 +1081,9 @@ declare namespace sap {
           /**
            * Toolbar of the `SimpleForm`.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored. If a title is needed inside the `Toolbar` it
-           * must be added at content to the `Toolbar`. In this case, add the `Title` to the `ariaLabelledBy` association.
+           * **Note:** If a `Toolbar` is used, the {@link #getTitle Title} is ignored. If a title is needed inside
+           * the `Toolbar` it must be added at content to the `Toolbar`. In this case, add the `Title` to the {@link #addAriaLabelledBy ariaLabelledBy }
+           * association. Use the right title level to meet the visual requirements. This might be theme-dependent.
            *
            * @since 1.36.0
            */
@@ -1091,8 +1093,9 @@ declare namespace sap {
            * Association to controls / IDs which label this control (see WAI-ARIA attribute `aria-labelledby`).
            *
            * **Note:** Every `Form` needs to have some title or label (at least for screen reader support). If no
-           * `Title` is set, and the `Form` is not a child or a control with a title, such as {@link sap.m.Panel Panel }
-           * or {@link sap.m.Dialog Dialog}, a label or title needs to be assigned using the `ariaLabelledBy` association.
+           * {@link #getTitle Title} is set, and the `SimpleForm` is not a child or a control with a title, such as
+           * {@link sap.m.Panel Panel} or {@link sap.m.Dialog Dialog}, a label or title needs to be assigned using
+           * the `ariaLabelledBy` association.
            *
            * @since 1.32.0
            */
@@ -1428,11 +1431,11 @@ declare namespace sap {
          * So the last row of the {@link sap.ui.layout.form.Form Form} control will not be fully used.
          *
          * The default size of the {@link sap.ui.layout.form.FormContainer FormContainer} element can be overwritten
-         * by using {@link sap.ui.layout.form.ColumnContainerData ColumnContainerData} as `LayoutData`. If one {@link sap.ui.layout.form.FormContainer FormContainer }
-         * element has {@link sap.ui.layout.form.ColumnContainerData ColumnContainerData} set, the size calculation
-         * of the other {@link sap.ui.layout.form.FormContainer FormContainer} elements might not lead to the expected
-         * result. In this case, use {@link sap.ui.layout.form.ColumnContainerData ColumnContainerData} also for
-         * the other {@link sap.ui.layout.form.FormContainer FormContainer} elements.
+         * by using {@link sap.ui.layout.form.ColumnContainerData ColumnContainerData} as {@link sap.ui.core.Element#setLayoutData LayoutData}.
+         * If one {@link sap.ui.layout.form.FormContainer FormContainer} element has {@link sap.ui.layout.form.ColumnContainerData ColumnContainerData }
+         * set, the size calculation of the other {@link sap.ui.layout.form.FormContainer FormContainer} elements
+         * might not lead to the expected result. In this case, use {@link sap.ui.layout.form.ColumnContainerData ColumnContainerData }
+         * also for the other {@link sap.ui.layout.form.FormContainer FormContainer} elements.
          *
          * The {@link sap.ui.layout.form.FormElement FormElement} elements are spread out to the columns of a {@link sap.ui.layout.form.FormContainer FormContainer }
          * element arranged in a newspaper-like order. The position of the labels and fields depends on the size
@@ -1685,8 +1688,8 @@ declare namespace sap {
          * UI requirements without changing the `Form` itself.
          *
          * 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`.
+         * allow simple switching of the {@link sap.ui.layout.form.FormLayout FormLayout}. {@link sap.ui.core.Element#setLayoutData 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.
@@ -1695,10 +1698,10 @@ declare namespace sap {
          * 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. In addition to that, wrong screen reader announcements
-         * might occur.
+         * If editable controls are used as content, the {@link #setEditable editable} property must be set to `true`,
+         * otherwise to `false`. If the {@link #setEditable editable} property is set incorrectly, there will be
+         * visual issues like wrong label alignment or wrong spacing between the controls. In addition to that,
+         * wrong screen reader announcements might occur.
          *
          * @since 1.16.0
          */
@@ -1834,7 +1837,7 @@ declare namespace sap {
            *
            * The labels inside the form will be rendered by default in the according mode.
            *
-           * **Note:** The setting of this property does not change the content of the form. For example, `Input`
+           * **Note:** The setting of this property does not change the content of the form. For example, {@link sap.m.Input Input }
            * controls in a form with `editable` set to false are still editable.
            *
            * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
@@ -1868,7 +1871,7 @@ declare namespace sap {
            * Title of the `Form`. Can either be a `Title` element or a string. If a `Title` element it used, the style
            * of the title can be set.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored.
+           * **Note:** If a {@link #getToolbar Toolbar} is used, the `Title` is ignored.
            *
            * **Note:** If the title is provided as a string, the title is rendered with a theme-dependent default
            * level. As the `Form` control cannot know the structure of the page, this might not fit the page structure.
@@ -1881,9 +1884,9 @@ declare namespace sap {
            *
            * Toolbar of the `Form`.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored. If a title is needed inside the `Toolbar` it
-           * must be added at content to the `Toolbar`. In this case, add the `Title` to the `ariaLabelledBy` association.
-           * Use the right title level to meet the visual requirements. This might be theme-dependent.
+           * **Note:** If a `Toolbar` is used, the {@link #getTitle Title} is ignored. If a title is needed inside
+           * the `Toolbar` it must be added at content to the `Toolbar`. In this case, add the `Title` to the {@link #addAriaLabelledBy ariaLabelledBy }
+           * association. Use the right title level to meet the visual requirements. This might be theme-dependent.
            *
            * @since 1.36.0
            */
@@ -1979,7 +1982,7 @@ declare namespace sap {
            *
            * The labels inside the form will be rendered by default in the according mode.
            *
-           * **Note:** The setting of this property does not change the content of the form. For example, `Input`
+           * **Note:** The setting of this property does not change the content of the form. For example, {@link sap.m.Input Input }
            * controls in a form with `editable` set to false are still editable.
            *
            * **Warning:** If this property is wrongly set, this might lead to visual issues. The labels and fields
@@ -2056,8 +2059,9 @@ declare namespace sap {
           ): this;
         }
         /**
-         * A `FormContainer` represents a group inside a `Form`. It consists of `FormElements`. The rendering of
-         * the `FormContainer` is done by the `FormLayout` assigned to the `Form`.
+         * A `FormContainer` represents a group inside a {@link sap.ui.layout.form.Form Form}. It consists of {@link sap.ui.layout.form.FormElement FormElements}.
+         * The rendering of the `FormContainer` is done by the {@link sap.ui.layout.form.Form#getLayout FormLayout }
+         * assigned to the {@link sap.ui.layout.form.Form Form}.
          *
          * @since 1.16.0
          */
@@ -2198,7 +2202,7 @@ declare namespace sap {
            *
            * Defines if the `FormContainer` is expandable.
            *
-           * **Note:** The expander icon will only be shown if a `title` is set for the `FormContainer`.
+           * **Note:** The expander icon will only be shown if a {@link #getTitle Title} is set for the `FormContainer`.
            *
            * Default value is `false`.
            *
@@ -2211,7 +2215,7 @@ declare namespace sap {
            *
            * Container is expanded.
            *
-           * **Note:** This property only works if `expandable` is set to `true`.
+           * **Note:** This property only works if {@link #getExpandable expandable} is set to `true`.
            *
            * Default value is `true`.
            *
@@ -2231,7 +2235,7 @@ declare namespace sap {
            * Title of the `FormContainer`. Can either be a `Title` element or a string. If a `Title` element is used,
            * the style of the title can be set.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored.
+           * **Note:** If a {@link #getToolbar Toolbar} is used, the `Title` is ignored.
            *
            * **Note:** If the title is provided as a string, the title is rendered with a theme-dependent default
            * level. As the `Form` control cannot know the structure of the page, this might not fit the page structure.
@@ -2244,9 +2248,9 @@ declare namespace sap {
            *
            * Toolbar of the `FormContainer`.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored. If a title is needed inside the `Toolbar` it
-           * must be added at content to the `Toolbar`. In this case add the `Title` to the `ariaLabelledBy` association.
-           * Use the right title level to meet the visual requirements. This might be theme-dependent.
+           * **Note:** If a `Toolbar` is used, the {@link #getTitle Title} is ignored. If a title is needed inside
+           * the `Toolbar` it must be added at content to the `Toolbar`. In this case add the `Title` to the {@link #addAriaLabelledBy ariaLabelledBy }
+           * association. Use the right title level to meet the visual requirements. This might be theme-dependent.
            *
            * @since 1.36.0
            */
@@ -2350,7 +2354,7 @@ declare namespace sap {
            *
            * Defines if the `FormContainer` is expandable.
            *
-           * **Note:** The expander icon will only be shown if a `title` is set for the `FormContainer`.
+           * **Note:** The expander icon will only be shown if a {@link #getTitle Title} is set for the `FormContainer`.
            *
            * When called with a value of `null` or `undefined`, the default value of the property will be restored.
            *
@@ -2370,7 +2374,7 @@ declare namespace sap {
            *
            * Container is expanded.
            *
-           * **Note:** This property only works if `expandable` is set to `true`.
+           * **Note:** This property only works if {@link #getExpandable expandable} is set to `true`.
            *
            * When called with a value of `null` or `undefined`, the default value of the property will be restored.
            *
@@ -2430,8 +2434,8 @@ declare namespace sap {
           ): this;
         }
         /**
-         * A `FormElement` represents a row in a `FormContainer`. A `FormElement` is a combination of one label
-         * and different controls associated to this label.
+         * A `FormElement` represents a row in a {@link sap.ui.layout.form.FormContainer FormContainer}. A `FormElement`
+         * is a combination of one label and different controls associated to this label.
          *
          * @since 1.16.0
          */
@@ -2531,7 +2535,7 @@ declare namespace sap {
            *
            * **Warning:** Do not put any layout or other container controls in here. This could damage the visual
            * layout, keyboard support and screen-reader support. Only form controls are allowed. Views are also not
-           * supported. Allowed controls implement the interface `sap.ui.core.IFormContent`.
+           * supported. Allowed controls implement the interface {@link sap.ui.core.IFormContent}.
            */
           getFields(): sap.ui.core.Control[];
           /**
@@ -4138,8 +4142,8 @@ declare namespace sap {
          * 	 - A new `Label` control starts a new row (`{@link sap.ui.layout.form.FormElement FormElement}`) in
          *     the form.
          * 	 - All other controls will be assigned to the row (`{@link sap.ui.layout.form.FormElement FormElement}`)
-         *     that started with the last label.  Use `LayoutData` to influence the layout for special cases in
-         *     the Input/Display controls.
+         *     that started with the last label.  Use {@link sap.ui.core.Element#setLayoutData LayoutData} to influence
+         *     the layout for special cases in the Input/Display controls.
          *
          * **Note:** If a more complex form is needed, use the `{@link sap.ui.layout.form.Form Form}` control instead.
          *
@@ -4391,18 +4395,19 @@ declare namespace sap {
            * The content of the form is structured in the following way:
            * 	 - 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}`).
+           * 	 - Add a {@link sap.m.Label Label} control to start a new row (`{@link sap.ui.layout.form.FormElement FormElement}`).
            *
            * 	 - Add controls as input fields, text fields or other as needed.
-           * 	 - 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 {@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}):
-           *
+           * 	 - Use {@link sap.ui.core.Element#setLayoutData LayoutData} to influence the layout for special cases
+           *     in the single controls. For example, if a {@link sap.ui.layout.ColumnLayout 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 {@link sap.ui.layout.form.ColumnElementData ColumnElementData }
+           *     to them via the {@link sap.ui.core.Element#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"});
@@ -4415,10 +4420,10 @@ declare namespace sap {
            * 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}):
+           * to them via the {@link sap.ui.core.Element#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"});
@@ -4429,12 +4434,12 @@ declare namespace sap {
            *
            * **Warning:** Do not put any layout or other container controls in here. This could damage the visual
            * layout, keyboard support and screen-reader support. Only labels, titles, toolbars and form controls are
-           * allowed. Views are also not supported. Allowed form controls implement the interface `sap.ui.core.IFormContent`.
+           * allowed. Views are also not supported. Allowed form controls implement the interface {@link sap.ui.core.IFormContent}.
            *
-           * 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. In addition to that, wrong screen reader announcements
-           * might occur.
+           * If editable controls are used as content, the {@link #setEditable editable} property must be set to `true`,
+           * otherwise to `false`. If the {@link #setEditable editable} property is set incorrectly, there will be
+           * visual issues like wrong label alignment or wrong spacing between the controls. In addition to that,
+           * wrong screen reader announcements might occur.
            */
           getContent(): sap.ui.core.Element[];
           /**
@@ -4676,7 +4681,7 @@ declare namespace sap {
            *
            * Title element of the `SimpleForm`. Can either be a `Title` element, or a string.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored.
+           * **Note:** If a {@link #getToolbar Toolbar} is used, the `Title` is ignored.
            *
            * **Note:** If the title is provided as a string, the title is rendered with a theme-dependent default
            * level. As the `Form` control cannot know the structure of the page, this might not fit the page structure.
@@ -4691,8 +4696,9 @@ declare namespace sap {
            *
            * Toolbar of the `SimpleForm`.
            *
-           * **Note:** If a `Toolbar` is used, the `Title` is ignored. If a title is needed inside the `Toolbar` it
-           * must be added at content to the `Toolbar`. In this case, add the `Title` to the `ariaLabelledBy` association.
+           * **Note:** If a `Toolbar` is used, the {@link #getTitle Title} is ignored. If a title is needed inside
+           * the `Toolbar` it must be added at content to the `Toolbar`. In this case, add the `Title` to the {@link #addAriaLabelledBy ariaLabelledBy }
+           * association. Use the right title level to meet the visual requirements. This might be theme-dependent.
            *
            * @since 1.36.0
            */