@ionic/core 7.3.4-dev.11699991837.1bc64f72 → 7.3.4-dev.11700516018.128deb56

package/dist/types/components/checkbox/checkbox.d.ts

@@ -51,9 +51,8 @@ export declare class Checkbox implements ComponentInterface {
    * `"start"`: The label will appear to the left of the checkbox in LTR and to the right in RTL.
    * `"end"`: The label will appear to the right of the checkbox in LTR and to the left in RTL.
    * `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
-   * `"stacked"`: The label will appear above the checkbox regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
    */
-  labelPlacement: 'start' | 'end' | 'fixed' | 'stacked';
+  labelPlacement: 'start' | 'end' | 'fixed';
   /**
    * How to pack the label and checkbox within a line.
    * `"start"`: The label and checkbox will appear on the left in LTR and
@@ -64,12 +63,6 @@ export declare class Checkbox implements ComponentInterface {
    * ends of the line with space between the two elements.
    */
   justify: 'start' | 'end' | 'space-between';
-  /**
-   * How to control the alignment of the checkbox and label on the cross axis.
-   * `"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL.
-   * `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-   */
-  alignment: 'start' | 'center';
   /**
    * Set the `legacy` property to `true` to forcibly use the legacy form control markup.
    * Ionic will only opt checkboxes in to the modern form markup when they are

package/dist/types/components/datetime/datetime.d.ts

@@ -18,12 +18,6 @@ import type { DatetimePresentation, DatetimeChangeEventDetail, DatetimeParts, Ti
  *
  * @part month-year-button - The button that opens the month/year picker when
  * using a grid style layout.
- *
- * @part calendar-day - The individual buttons that display a day inside of the datetime
- * calendar.
- * @part calendar-day active - The currently selected calendar day.
- * @part calendar-day today - The calendar day that contains the current day.
- * @part calendar-day disabled - The calendar day that is disabled.
  */
 export declare class Datetime implements ComponentInterface {
   private inputId;
@@ -43,22 +37,16 @@ export declare class Datetime implements ComponentInterface {
   private todayParts;
   private defaultParts;
   private prevPresentation;
-  private resolveForceDateScrolling?;
+  /**
+   * Duplicate reference to `activeParts` that does not trigger a re-render of the component.
+   * Allows caching an instance of the `activeParts` in between render cycles.
+   */
+  private activePartsClone;
   showMonthAndYear: boolean;
   activeParts: DatetimeParts | DatetimeParts[];
   workingParts: DatetimeParts;
   el: HTMLIonDatetimeElement;
   isTimePopoverOpen: boolean;
-  /**
-   * When defined, will force the datetime to render the month
-   * containing the specified date. Currently, this should only
-   * be used to enable immediately auto-scrolling to the new month,
-   * and should then be reset to undefined once the transition is
-   * finished and the forced month is now in view.
-   *
-   * Applies to grid-style datetimes only.
-   */
-  forceRenderDate?: DatetimeParts;
   /**
    * The color to use from your application's color palette.
    * Default options are: `"primary"`, `"secondary"`, `"tertiary"`, `"success"`, `"warning"`, `"danger"`, `"light"`, `"medium"`, and `"dark"`.
@@ -120,7 +108,6 @@ export declare class Datetime implements ComponentInterface {
    * `"time-date"` will show the time picker first and date picker second.
    */
   presentation: DatetimePresentation;
-  private get isGridStyle();
   /**
    * The text to display on the picker's cancel button.
    */
@@ -179,6 +166,7 @@ export declare class Datetime implements ComponentInterface {
    */
   minuteValues?: number[] | number | string;
   protected minuteValuesChanged(): void;
+  protected activePartsChanged(): void;
   /**
    * The locale to use for `ion-datetime`. This
    * impacts month and day name formatting.
@@ -221,7 +209,7 @@ export declare class Datetime implements ComponentInterface {
   /**
    * Update the datetime value when the value changes
    */
-  protected valueChanged(): Promise<void>;
+  protected valueChanged(): void;
   /**
    * If `true`, a header will be shown above the calendar
    * picker. This will include both the slotted title, and
@@ -338,9 +326,9 @@ export declare class Datetime implements ComponentInterface {
    * data. This should be used when rendering an
    * interface in an environment where the `value`
    * may not be set. This function works
-   * by returning the first selected date and then
-   * falling back to defaultParts if no active date
-   * is selected.
+   * by returning the first selected date in
+   * "activePartsClone" and then falling back to
+   * defaultParts if no active date is selected.
    */
   private getActivePartsWithFallback;
   private getActivePart;
@@ -369,7 +357,6 @@ export declare class Datetime implements ComponentInterface {
    */
   componentDidRender(): void;
   private processValue;
-  private animateToDate;
   componentWillLoad(): void;
   private emitStyle;
   private onFocus;

package/dist/types/components/datetime/utils/data.d.ts

@@ -45,7 +45,7 @@ export declare const generateTime: (refParts: DatetimeParts, hourCycle?: 'h12' |
  * Given DatetimeParts, generate the previous,
  * current, and and next months.
  */
-export declare const generateMonths: (refParts: DatetimeParts, forcedDate?: DatetimeParts) => DatetimeParts[];
+export declare const generateMonths: (refParts: DatetimeParts) => DatetimeParts[];
 export declare const getMonthColumnData: (locale: string, refParts: DatetimeParts, minParts?: DatetimeParts, maxParts?: DatetimeParts, monthValues?: number[], formatOptions?: Intl.DateTimeFormatOptions) => PickerColumnItem[];
 /**
  * Returns information regarding

package/dist/types/components/datetime/utils/parse.d.ts

@@ -15,10 +15,10 @@ export declare const getPartsFromCalendarDay: (el: HTMLElement) => DatetimeParts
  * We do not use the JS Date object here because
  * it adjusts the date for the current timezone.
  */
-export declare function parseDate(val: string): DatetimeParts | undefined;
-export declare function parseDate(val: string[]): DatetimeParts[] | undefined;
+export declare function parseDate(val: string): DatetimeParts;
+export declare function parseDate(val: string[]): DatetimeParts[];
 export declare function parseDate(val: undefined | null): undefined;
-export declare function parseDate(val: string | string[]): DatetimeParts | DatetimeParts[] | undefined;
+export declare function parseDate(val: string | string[]): DatetimeParts | DatetimeParts[];
 export declare function parseDate(val: string | string[] | undefined | null): DatetimeParts | DatetimeParts[] | undefined;
 export declare const clampDate: (dateParts: DatetimeParts, minParts?: DatetimeParts, maxParts?: DatetimeParts) => DatetimeParts;
 /**

package/dist/types/components/radio/radio.d.ts

@@ -48,9 +48,8 @@ export declare class Radio implements ComponentInterface {
    * `"start"`: The label will appear to the left of the radio in LTR and to the right in RTL.
    * `"end"`: The label will appear to the right of the radio in LTR and to the left in RTL.
    * `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
-   * `"stacked"`: The label will appear above the radio regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
    */
-  labelPlacement: 'start' | 'end' | 'fixed' | 'stacked';
+  labelPlacement: 'start' | 'end' | 'fixed';
   /**
    * Set the `legacy` property to `true` to forcibly use the legacy form control markup.
    * Ionic will only opt components in to the modern form markup when they are
@@ -71,12 +70,6 @@ export declare class Radio implements ComponentInterface {
    * ends of the line with space between the two elements.
    */
   justify: 'start' | 'end' | 'space-between';
-  /**
-   * How to control the alignment of the radio and label on the cross axis.
-   * `"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL.
-   * `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-   */
-  alignment: 'start' | 'center';
   /**
    * Emitted when the styles change.
    * @internal

package/dist/types/components/range/range.d.ts

@@ -116,9 +116,8 @@ export declare class Range implements ComponentInterface {
    * `"start"`: The label will appear to the left of the range in LTR and to the right in RTL.
    * `"end"`: The label will appear to the right of the range in LTR and to the left in RTL.
    * `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
-   * `"stacked"`: The label will appear above the range regardless of the direction.
    */
-  labelPlacement: 'start' | 'end' | 'fixed' | 'stacked';
+  labelPlacement: 'start' | 'end' | 'fixed';
   /**
    * Set the `legacy` property to `true` to forcibly use the legacy form control markup.
    * Ionic will only opt components in to the modern form markup when they are

package/dist/types/components/toast/toast-interface.d.ts

@@ -27,9 +27,6 @@ export interface ToastButton {
   icon?: string;
   side?: 'start' | 'end';
   role?: 'cancel' | string;
-  /**
-   * @deprecated Use the toast button's CSS Shadow Parts instead.
-   */
   cssClass?: string | string[];
   htmlAttributes?: {
     [key: string]: any;

package/dist/types/components/toggle/toggle.d.ts

@@ -56,9 +56,8 @@ export declare class Toggle implements ComponentInterface {
    * `"start"`: The label will appear to the left of the toggle in LTR and to the right in RTL.
    * `"end"`: The label will appear to the right of the toggle in LTR and to the left in RTL.
    * `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
-   * `"stacked"`: The label will appear above the toggle regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
    */
-  labelPlacement: 'start' | 'end' | 'fixed' | 'stacked';
+  labelPlacement: 'start' | 'end' | 'fixed';
   /**
    * Set the `legacy` property to `true` to forcibly use the legacy form control markup.
    * Ionic will only opt components in to the modern form markup when they are
@@ -79,12 +78,6 @@ export declare class Toggle implements ComponentInterface {
    * ends of the line with space between the two elements.
    */
   justify: 'start' | 'end' | 'space-between';
-  /**
-   * How to control the alignment of the toggle and label on the cross axis.
-   * ``"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL.
-   * `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-   */
-  alignment: 'start' | 'center';
   /**
    * Emitted when the user switches the toggle on or off. Does not emit
    * when programmatically changing the value of the `checked` property.

package/dist/types/components.d.ts

@@ -602,10 +602,6 @@ export namespace Components {
         "mode"?: "ios" | "md";
     }
     interface IonCheckbox {
-        /**
-          * How to control the alignment of the checkbox and label on the cross axis. `"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL. `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-         */
-        "alignment": 'start' | 'center';
         /**
           * If `true`, the checkbox is selected.
          */
@@ -627,9 +623,9 @@ export namespace Components {
          */
         "justify": 'start' | 'end' | 'space-between';
         /**
-          * Where to place the label relative to the checkbox. `"start"`: The label will appear to the left of the checkbox in LTR and to the right in RTL. `"end"`: The label will appear to the right of the checkbox in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the checkbox regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
+          * Where to place the label relative to the checkbox. `"start"`: The label will appear to the left of the checkbox in LTR and to the right in RTL. `"end"`: The label will appear to the right of the checkbox in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement": 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement": 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt checkboxes in to the modern form markup when they are using either the `aria-label` attribute or have text in the default slot. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior.  Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */
@@ -2220,10 +2216,6 @@ export namespace Components {
         "value": number;
     }
     interface IonRadio {
-        /**
-          * How to control the alignment of the radio and label on the cross axis. `"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL. `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-         */
-        "alignment": 'start' | 'center';
         /**
           * The color to use from your application's color palette. Default options are: `"primary"`, `"secondary"`, `"tertiary"`, `"success"`, `"warning"`, `"danger"`, `"light"`, `"medium"`, and `"dark"`. For more information on colors, see [theming](/docs/theming/basics).
          */
@@ -2237,9 +2229,9 @@ export namespace Components {
          */
         "justify": 'start' | 'end' | 'space-between';
         /**
-          * Where to place the label relative to the radio. `"start"`: The label will appear to the left of the radio in LTR and to the right in RTL. `"end"`: The label will appear to the right of the radio in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the radio regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
+          * Where to place the label relative to the radio. `"start"`: The label will appear to the left of the radio in LTR and to the right in RTL. `"end"`: The label will appear to the right of the radio in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement": 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement": 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt components in to the modern form markup when they are using either the `aria-label` attribute or the default slot that contains the label text. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior. Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */
@@ -2299,9 +2291,9 @@ export namespace Components {
          */
         "label"?: string;
         /**
-          * Where to place the label relative to the range. `"start"`: The label will appear to the left of the range in LTR and to the right in RTL. `"end"`: The label will appear to the right of the range in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the range regardless of the direction.
+          * Where to place the label relative to the range. `"start"`: The label will appear to the left of the range in LTR and to the right in RTL. `"end"`: The label will appear to the right of the range in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement": 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement": 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt components in to the modern form markup when they are using either the `aria-label` attribute or the `label` property. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior. Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */
@@ -3173,10 +3165,6 @@ export namespace Components {
         "trigger": string | undefined;
     }
     interface IonToggle {
-        /**
-          * How to control the alignment of the toggle and label on the cross axis. ``"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL. `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-         */
-        "alignment": 'start' | 'center';
         /**
           * If `true`, the toggle is selected.
          */
@@ -3198,9 +3186,9 @@ export namespace Components {
          */
         "justify": 'start' | 'end' | 'space-between';
         /**
-          * Where to place the label relative to the input. `"start"`: The label will appear to the left of the toggle in LTR and to the right in RTL. `"end"`: The label will appear to the right of the toggle in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the toggle regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
+          * Where to place the label relative to the input. `"start"`: The label will appear to the left of the toggle in LTR and to the right in RTL. `"end"`: The label will appear to the right of the toggle in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement": 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement": 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt components in to the modern form markup when they are using either the `aria-label` attribute or the default slot that contains the label text. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior. Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */
@@ -4620,10 +4608,6 @@ declare namespace LocalJSX {
         "mode"?: "ios" | "md";
     }
     interface IonCheckbox {
-        /**
-          * How to control the alignment of the checkbox and label on the cross axis. `"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL. `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-         */
-        "alignment"?: 'start' | 'center';
         /**
           * If `true`, the checkbox is selected.
          */
@@ -4645,9 +4629,9 @@ declare namespace LocalJSX {
          */
         "justify"?: 'start' | 'end' | 'space-between';
         /**
-          * Where to place the label relative to the checkbox. `"start"`: The label will appear to the left of the checkbox in LTR and to the right in RTL. `"end"`: The label will appear to the right of the checkbox in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the checkbox regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
+          * Where to place the label relative to the checkbox. `"start"`: The label will appear to the left of the checkbox in LTR and to the right in RTL. `"end"`: The label will appear to the right of the checkbox in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement"?: 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement"?: 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt checkboxes in to the modern form markup when they are using either the `aria-label` attribute or have text in the default slot. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior.  Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */
@@ -6143,10 +6127,6 @@ declare namespace LocalJSX {
         "value"?: number;
     }
     interface IonRadio {
-        /**
-          * How to control the alignment of the radio and label on the cross axis. `"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL. `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-         */
-        "alignment"?: 'start' | 'center';
         /**
           * The color to use from your application's color palette. Default options are: `"primary"`, `"secondary"`, `"tertiary"`, `"success"`, `"warning"`, `"danger"`, `"light"`, `"medium"`, and `"dark"`. For more information on colors, see [theming](/docs/theming/basics).
          */
@@ -6160,9 +6140,9 @@ declare namespace LocalJSX {
          */
         "justify"?: 'start' | 'end' | 'space-between';
         /**
-          * Where to place the label relative to the radio. `"start"`: The label will appear to the left of the radio in LTR and to the right in RTL. `"end"`: The label will appear to the right of the radio in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the radio regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
+          * Where to place the label relative to the radio. `"start"`: The label will appear to the left of the radio in LTR and to the right in RTL. `"end"`: The label will appear to the right of the radio in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement"?: 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement"?: 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt components in to the modern form markup when they are using either the `aria-label` attribute or the default slot that contains the label text. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior. Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */
@@ -6232,9 +6212,9 @@ declare namespace LocalJSX {
          */
         "label"?: string;
         /**
-          * Where to place the label relative to the range. `"start"`: The label will appear to the left of the range in LTR and to the right in RTL. `"end"`: The label will appear to the right of the range in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the range regardless of the direction.
+          * Where to place the label relative to the range. `"start"`: The label will appear to the left of the range in LTR and to the right in RTL. `"end"`: The label will appear to the right of the range in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement"?: 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement"?: 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt components in to the modern form markup when they are using either the `aria-label` attribute or the `label` property. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior. Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */
@@ -7163,10 +7143,6 @@ declare namespace LocalJSX {
         "trigger"?: string | undefined;
     }
     interface IonToggle {
-        /**
-          * How to control the alignment of the toggle and label on the cross axis. ``"start"`: The label and control will appear on the left of the cross axis in LTR, and on the right side in RTL. `"center"`: The label and control will appear at the center of the cross axis in both LTR and RTL.
-         */
-        "alignment"?: 'start' | 'center';
         /**
           * If `true`, the toggle is selected.
          */
@@ -7188,9 +7164,9 @@ declare namespace LocalJSX {
          */
         "justify"?: 'start' | 'end' | 'space-between';
         /**
-          * Where to place the label relative to the input. `"start"`: The label will appear to the left of the toggle in LTR and to the right in RTL. `"end"`: The label will appear to the right of the toggle in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("..."). `"stacked"`: The label will appear above the toggle regardless of the direction. The alignment of the label can be controlled with the `alignment` property.
+          * Where to place the label relative to the input. `"start"`: The label will appear to the left of the toggle in LTR and to the right in RTL. `"end"`: The label will appear to the right of the toggle in LTR and to the left in RTL. `"fixed"`: The label has the same behavior as `"start"` except it also has a fixed width. Long text will be truncated with ellipses ("...").
          */
-        "labelPlacement"?: 'start' | 'end' | 'fixed' | 'stacked';
+        "labelPlacement"?: 'start' | 'end' | 'fixed';
         /**
           * Set the `legacy` property to `true` to forcibly use the legacy form control markup. Ionic will only opt components in to the modern form markup when they are using either the `aria-label` attribute or the default slot that contains the label text. As a result, the `legacy` property should only be used as an escape hatch when you want to avoid this automatic opt-in behavior. Note that this property will be removed in an upcoming major release of Ionic, and all form components will be opted-in to using the modern form markup.
          */

package/dist/types/index.d.ts

@@ -1,6 +1,5 @@
 import 'ionicons';
 export { createAnimation } from './utils/animation/animation';
-export { getIonPageElement } from './utils/transition';
 export { iosTransitionAnimation } from './utils/transition/ios.transition';
 export { mdTransitionAnimation } from './utils/transition/md.transition';
 export { getTimeGivenProgression } from './utils/animation/cubic-bezier';

package/dist/types/interface.d.ts

@@ -43,7 +43,6 @@ export {
   AnimationKeyFrames,
   AnimationLifecycle,
 } from './utils/animation/animation-interface';
-export { TransitionOptions } from './utils/transition';
 export { HTMLIonOverlayElement, OverlayController, OverlayInterface } from './utils/overlays-interface';
 export { Config, config } from './global/config';
 export { Gesture, GestureConfig, GestureDetail } from './utils/gesture';