@openui5/types 1.126.0 → 1.127.0

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.126.0
+// For Library Version: 1.127.0
 
 declare module "sap/ui/layout/library" {
   import Control from "sap/ui/core/Control";
@@ -6718,7 +6718,7 @@ declare module "sap/ui/layout/form/Form" {
      *
      * **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.
-     * In this case provide the title using a `Title` element and set its {@link sap.ui.core.Title#setLevel level }
+     * In this case, provide the title using a `Title` element and set its {@link sap.ui.core.Title#setLevel level }
      * to the needed value.
      */
     getTitle(): Title | string;
@@ -6728,7 +6728,7 @@ declare module "sap/ui/layout/form/Form" {
      * 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.
+     * 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.
      *
      * @since 1.36.0
@@ -6944,7 +6944,7 @@ declare module "sap/ui/layout/form/Form" {
      *
      * **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.
-     * In this case provide the title using a `Title` element and set its {@link sap.ui.core.Title#setLevel level }
+     * In this case, provide the title using a `Title` element and set its {@link sap.ui.core.Title#setLevel level }
      * to the needed value.
      */
     title?: string | Title | PropertyBindingInfo;
@@ -6953,7 +6953,7 @@ declare module "sap/ui/layout/form/Form" {
      * 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.
+     * 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.
      *
      * @since 1.36.0
@@ -6969,6 +6969,10 @@ declare module "sap/ui/layout/form/Form" {
     /**
      * 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 }
+     * or {@link sap.m.Dialog Dialog}, a label or title needs to be assigned using the `ariaLabelledBy` association.
+     *
      * @since 1.28.0
      */
     ariaLabelledBy?: Array<Control | string>;
@@ -7429,6 +7433,10 @@ declare module "sap/ui/layout/form/FormContainer" {
      * **Note:** This attribute is only rendered if the `FormContainer` has it's own DOM representation in the
      * 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.
+     *
      * @since 1.36.0
      */
     ariaLabelledBy?: Array<Control | string>;
@@ -10075,6 +10083,13 @@ declare module "sap/ui/layout/form/SimpleForm" {
      *
      * 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 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.
+     * In this case, provide the title using a `Title` element and set its {@link sap.ui.core.Title#setLevel level }
+     * to the needed value.
+     *
      * @since 1.16.3
      */
     getTitle(): Title | string;
@@ -10084,7 +10099,7 @@ declare module "sap/ui/layout/form/SimpleForm" {
      * 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.
+     * must be added at content to the `Toolbar`. In this case, add the `Title` to the `ariaLabelledBy` association.
      *
      * @since 1.36.0
      */
@@ -11041,6 +11056,13 @@ declare module "sap/ui/layout/form/SimpleForm" {
     /**
      * 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 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.
+     * In this case, provide the title using a `Title` element and set its {@link sap.ui.core.Title#setLevel level }
+     * to the needed value.
+     *
      * @since 1.16.3
      */
     title?: string | Title | PropertyBindingInfo;
@@ -11049,7 +11071,7 @@ declare module "sap/ui/layout/form/SimpleForm" {
      * 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.
+     * must be added at content to the `Toolbar`. In this case, add the `Title` to the `ariaLabelledBy` association.
      *
      * @since 1.36.0
      */
@@ -11058,6 +11080,10 @@ declare module "sap/ui/layout/form/SimpleForm" {
     /**
      * 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.
+     *
      * @since 1.32.0
      */
     ariaLabelledBy?: Array<Control | string>;
@@ -14977,6 +15003,9 @@ declare module "sap/ui/layout/VerticalLayout" {
   /**
    * In this layout the content controls are rendered one below the other.
    *
+   * **Note:** `VerticalLayout` is not a focusable element and therefore the inheritance of the `tooltip`
+   * property isn't supported.
+   *
    * @since 1.16.0
    */
   export default class VerticalLayout extends Control {

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.126.0
+// For Library Version: 1.127.0
 
 declare module "sap/ui/mdc/AggregationBaseDelegate" {
   import BaseDelegate from "sap/ui/mdc/BaseDelegate";
@@ -4278,6 +4278,10 @@ declare module "sap/ui/mdc/Chart" {
      * on a selectionDetails popover
      */
     unitPath?: object;
+    /**
+     * The timeUnit type for a TimeDimension
+     */
+    timeUnitType?: object;
   };
 
   /**
@@ -20430,6 +20434,11 @@ declare module "sap/ui/mdc/ValueHelp" {
      * ID of the navigated item. (This is needed to set the corresponding aria-attribute)
      */
     itemId?: string;
+
+    /**
+     * If `true` the filtering was executed case sensitive
+     */
+    caseSensitive?: boolean;
   }
 
   /**
@@ -20546,6 +20555,11 @@ declare module "sap/ui/mdc/ValueHelp" {
      */
     itemId?: string;
 
+    /**
+     * Number of found items
+     */
+    items?: int;
+
     /**
      * If `true` the filtering was executed case sensitive
      */
@@ -20559,6 +20573,19 @@ declare module "sap/ui/mdc/ValueHelp" {
     ValueHelp$TypeaheadSuggestedEventParameters,
     ValueHelp
   >;
+
+  /**
+   * Parameters of the ValueHelp#visualFocusSet event.
+   */
+  export interface ValueHelp$VisualFocusSetEventParameters {}
+
+  /**
+   * Event object of the ValueHelp#visualFocusSet event.
+   */
+  export type ValueHelp$VisualFocusSetEvent = Event<
+    ValueHelp$VisualFocusSetEventParameters,
+    ValueHelp
+  >;
 }
 
 declare module "sap/ui/mdc/valuehelp/base/Container" {
@@ -20858,6 +20885,17 @@ declare module "sap/ui/mdc/valuehelp/base/Container" {
        */
       oEvent: Event
     ): void;
+    /**
+     * Handles the `visualFocusSet` event of the content.
+     *
+     * @ui5-protected Do not call from applications (only from related classes in the framework)
+     */
+    handleVisualFocusSet(
+      /**
+       * event
+       */
+      oEvent: Event
+    ): void;
     /**
      * Checks for the provided `sap.ui.mdc.valuehelp.base.Content` in the aggregation {@link #getContent content}.
      * and returns its index if found or -1 otherwise.
@@ -21078,6 +21116,11 @@ declare module "sap/ui/mdc/valuehelp/base/Container" {
      * ID of the navigated item. (This is needed to set the corresponding aria-attribute)
      */
     itemId?: string;
+
+    /**
+     * If `true` the filtering was executed case sensitive
+     */
+    caseSensitive?: boolean;
   }
 
   /**
@@ -21183,6 +21226,11 @@ declare module "sap/ui/mdc/valuehelp/base/Container" {
      */
     itemId?: string;
 
+    /**
+     * Number of found items
+     */
+    items?: int;
+
     /**
      * If `true` the filtering was executed case sensitive
      */
@@ -21196,6 +21244,19 @@ declare module "sap/ui/mdc/valuehelp/base/Container" {
     Container$TypeaheadSuggestedEventParameters,
     Container
   >;
+
+  /**
+   * Parameters of the Container#visualFocusSet event.
+   */
+  export interface Container$VisualFocusSetEventParameters {}
+
+  /**
+   * Event object of the Container#visualFocusSet event.
+   */
+  export type Container$VisualFocusSetEvent = Event<
+    Container$VisualFocusSetEventParameters,
+    Container
+  >;
 }
 
 declare module "sap/ui/mdc/valuehelp/base/Content" {
@@ -21645,6 +21706,11 @@ declare module "sap/ui/mdc/valuehelp/base/Content" {
      * ID of the navigated item. (This is needed to set the corresponding aria-attribute)
      */
     itemId?: string;
+
+    /**
+     * If `true` the filtering was executed case sensitive
+     */
+    caseSensitive?: boolean;
   }
 
   /**
@@ -21714,6 +21780,11 @@ declare module "sap/ui/mdc/valuehelp/base/Content" {
      */
     itemId?: string;
 
+    /**
+     * Number of found items
+     */
+    items?: int;
+
     /**
      * If `true` the filtering was executed case sensitive
      */
@@ -21727,6 +21798,19 @@ declare module "sap/ui/mdc/valuehelp/base/Content" {
     Content$TypeaheadSuggestedEventParameters,
     Content
   >;
+
+  /**
+   * Parameters of the Content#visualFocusSet event.
+   */
+  export interface Content$VisualFocusSetEventParameters {}
+
+  /**
+   * Event object of the Content#visualFocusSet event.
+   */
+  export type Content$VisualFocusSetEvent = Event<
+    Content$VisualFocusSetEventParameters,
+    Content
+  >;
 }
 
 declare module "sap/ui/mdc/valuehelp/base/FilterableListContent" {

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.126.0
+// For Library Version: 1.127.0
 
 declare module "sap/ui/rta/api/startAdaptation" {
   import Control from "sap/ui/core/Control";
@@ -8,7 +8,9 @@ declare module "sap/ui/rta/api/startAdaptation" {
   /**
    * Starts UI adaptation, initiated for an application at the passed root control instance. With this API
    * you are also able to modify the UI adaptation plugins list and or add some event handler functions to
-   * be called on start, failed and stop events.
+   * be called on start, failed and stop events. CAUTION: In the key user layer (CUSTOMER) the adaptation
+   * mode starts automatically after a reload triggered by the adaptation mode (e.g. due to personalization
+   * changes or versioning). In this case the RuntimeAuthoring class will be started with default parameters.
    *
    * @since 1.83
    *

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.126.0
+// For Library Version: 1.127.0
 
 declare module "sap/ui/suite/library" {
   /**

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.126.0
+// For Library Version: 1.127.0
 
 declare module "sap/ui/support/library" {
   /**

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.126.0
+// For Library Version: 1.127.0
 
 declare module "sap/ui/table/library" {
   import TreeAutoExpandMode1 from "sap/ui/model/TreeAutoExpandMode";
@@ -5327,15 +5327,15 @@ declare module "sap/ui/table/rowmodes/Type" {
    */
   enum Type {
     /**
-     * Equivalent to the default configuration of {@link module:sap/ui/table/rowmodes/Auto}
+     * Equivalent to the default configuration of {@link sap.ui.table.rowmodes.Auto}
      */
     Auto = "Auto",
     /**
-     * Equivalent to the default configuration of {@link module:sap/ui/table/rowmodes/Fixed}
+     * Equivalent to the default configuration of {@link sap.ui.table.rowmodes.Fixed}
      */
     Fixed = "Fixed",
     /**
-     * Equivalent to the default configuration of {@link module:sap/ui/table/rowmodes/Interactive}
+     * Equivalent to the default configuration of {@link sap.ui.table.rowmodes.Interactive}
      */
     Interactive = "Interactive",
   }
@@ -5641,8 +5641,10 @@ declare module "sap/ui/table/Table" {
    * This allows the Table control to handle huge amounts of data. Nevertheless, restrictions apply regarding
    * the number of displayed columns. Keep the number as low as possible to improve performance. Due to the
    * nature of tables, the used control for column templates also has a big influence on the performance.
-   *   The Table control relies completely on data binding, and its supported feature set is tightly
-   * coupled to the data model and binding being used.
+   * Because of the described reuse of the controls during scrolling, all data-related changes must be based
+   * on bindings. Static changes, such as calling mutator functions or defining a one-time binding, must be
+   * avoided.   The Table control relies completely on data binding, and its supported feature set
+   * is tightly coupled to the data model and binding being used.
    */
   export default class Table extends Control {
     /**
@@ -7648,6 +7650,10 @@ declare module "sap/ui/table/Table" {
      *
      * Flag to enable or disable column reordering
      *
+     * **Note**: Column reordering is possible via drag&drop and keyboard shortcuts. Single-pointer alternative
+     * is not provided out-of-the-box and should be implemented on application side. For example the {@link sap.m.p13n.Engine }
+     * can be used, see the following sample: {@link https://ui5.sap.com/#/entity/sap.ui.table.Table/sample/sap.m.sample.p13n.EngineGridTable Personalization for grid table}.
+     *
      * Default value is `true`.
      *
      *
@@ -8540,6 +8546,10 @@ declare module "sap/ui/table/Table" {
      *
      * Flag to enable or disable column reordering
      *
+     * **Note**: Column reordering is possible via drag&drop and keyboard shortcuts. Single-pointer alternative
+     * is not provided out-of-the-box and should be implemented on application side. For example the {@link sap.m.p13n.Engine }
+     * can be used, see the following sample: {@link https://ui5.sap.com/#/entity/sap.ui.table.Table/sample/sap.m.sample.p13n.EngineGridTable Personalization for grid table}.
+     *
      * When called with a value of `null` or `undefined`, the default value of the property will be restored.
      *
      * Default value is `true`.
@@ -9294,6 +9304,10 @@ declare module "sap/ui/table/Table" {
 
     /**
      * Flag to enable or disable column reordering
+     *
+     * **Note**: Column reordering is possible via drag&drop and keyboard shortcuts. Single-pointer alternative
+     * is not provided out-of-the-box and should be implemented on application side. For example the {@link sap.m.p13n.Engine }
+     * can be used, see the following sample: {@link https://ui5.sap.com/#/entity/sap.ui.table.Table/sample/sap.m.sample.p13n.EngineGridTable Personalization for grid table}.
      */
     enableColumnReordering?: boolean | PropertyBindingInfo | `{${string}}`;
 

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

@@ -1,4 +1,4 @@
-// For Library Version: 1.126.0
+// For Library Version: 1.127.0
 
 declare module "sap/ui/testrecorder/library" {}