chore: build

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@capacitor/core](https://capacitorjs.com)
([source](https://togithub.com/ionic-team/capacitor)) | [`5.7.3` ->
`5.7.4`](https://renovatebot.com/diffs/npm/@capacitor%2fcore/5.7.3/5.7.4)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@capacitor%2fcore/5.7.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@capacitor%2fcore/5.7.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@capacitor%2fcore/5.7.3/5.7.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@capacitor%2fcore/5.7.3/5.7.4?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>ionic-team/capacitor (@&#8203;capacitor/core)</summary>

###
[`v5.7.4`](https://togithub.com/ionic-team/capacitor/releases/tag/5.7.4)

[Compare
Source](https://togithub.com/ionic-team/capacitor/compare/5.7.3...5.7.4)

##### Bug Fixes

- **http:** change proxy url generation
([30a32f4](30a32f467f))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "every weekday before 11am" (UTC),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Never, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/ionic-team/ionic-framework).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNjkuMiIsInVwZGF0ZWRJblZlciI6IjM3LjI2OS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

.github/COMPONENT-GUIDE.md

@@ -2,10 +2,10 @@
 
 - [Button States](#button-states)
   * [Component Structure](#component-structure)
-  * [Activated](#activated)
   * [Disabled](#disabled)
   * [Focused](#focused)
   * [Hover](#hover)
+  * [Activated](#activated)
   * [Ripple Effect](#ripple-effect)
   * [Example Components](#example-components)
   * [References](#references)
@@ -21,7 +21,7 @@
 
 ## Button States
 
-Any component that renders a button should have the following states: [`activated`](#activated), [`disabled`](#disabled), [`focused`](#focused), [`hover`](#hover). It should also have a [Ripple Effect](#ripple-effect) component added for Material Design.
+Any component that renders a button should have the following states: [`disabled`](#disabled), [`focused`](#focused), [`hover`](#hover), [`activated`](#activated). It should also have a [Ripple Effect](#ripple-effect) component added for Material Design.
 
 ### Component Structure
 
@@ -89,78 +89,6 @@ The following styles should be set for the CSS to work properly. Note that the `
 ```
 
 
-### Activated
-
-The activated state should be enabled for elements with actions on "press". It usually changes the opacity or background of an element.
-
-> [!WARNING]
->`:active` should not be used here as it is not received on mobile Safari unless the element has a `touchstart` listener (which we don't necessarily want to have to add to every element). From [Safari Web Content Guide](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/AdjustingtheTextSize/AdjustingtheTextSize.html):
->
->> On iOS, mouse events are sent so quickly that the down or active state is never received. Therefore, the `:active` pseudo state is triggered only when there is a touch event set on the HTML element
-
-> Make sure the component has the correct [component structure](#component-structure) before continuing.
-
-#### JavaScript
-
-The `ion-activatable` class needs to be set on an element that can be activated:
-
-```jsx
-render() {
-  return (
-    <Host class='ion-activatable'>
-      <slot></slot>
-    </Host>
-  );
-}
-```
-
-Once that is done, the element will get the `ion-activated` class added on press after a small delay. This delay exists so that the active state does not show up when an activatable element is tapped while scrolling.
-
-In addition to setting that class, `ion-activatable-instant` can be set in order to have an instant press with no delay:
-
-```jsx
-<Host class='ion-activatable ion-activatable-instant'>
-```
-
-#### CSS
-
-```css
- /**
-   * @prop --color-activated: Color of the button when pressed
-   * @prop --background-activated: Background of the button when pressed
-   * @prop --background-activated-opacity: Opacity of the background when pressed
-   */
-```
-
-Style the `ion-activated` class based on the spec for that element:
-
-```scss
-:host(.ion-activated) .button-native {
-  color: var(--color-activated);
-
-  &::after {
-    background: var(--background-activated);
-
-    opacity: var(--background-activated-opacity);
-  }
-}
-```
-
-> Order is important! Activated should be after the focused & hover states.
-
-
-#### User Customization
-
-Setting the activated state on the `::after` pseudo-element allows the user to customize the activated state without knowing what the default opacity is set at. A user can customize in the following ways to have a solid red background on press, or they can leave out `--background-activated-opacity` and the button will use the default activated opacity to match the spec.
-
-```css
-ion-button {
-  --background-activated: red;
-  --background-activated-opacity: 1;
-}
-```
-
-
 ### Disabled
 
 The disabled state should be set via prop on all components that render a native button. Setting a disabled state will change the opacity or color of the button and remove click events from firing.
@@ -197,7 +125,8 @@ render() {
 }
 ```
 
-> Note: if the class being added was for `ion-back-button` it would be `back-button-disabled`.
+> [!NOTE]
+> If the class being added was for `ion-back-button` it would be `back-button-disabled`.
 
 #### CSS
 
@@ -215,9 +144,10 @@ The following CSS _at the bare minimum_ should be added for the disabled class,
 
 TODO
 
+
 ### Focused
 
-The focused state should be enabled for elements with actions when tabbed to via the keyboard. This will only work inside of an `ion-app`. It usually changes the opacity or background of an element. 
+The focused state should be enabled for elements with actions when tabbed to via the keyboard. This will only work inside of an `ion-app`. It usually changes the opacity or background of an element.
 
 > [!WARNING]
 > Do not use `:focus` because that will cause the focus to apply even when an element is tapped (because the element is now focused). Instead, we only want the focus state to be shown when it makes sense which is what the `.ion-focusable` utility mentioned below does.
@@ -225,6 +155,7 @@ The focused state should be enabled for elements with actions when tabbed to via
 > [!NOTE]
 > The [`:focus-visible`](https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible) pseudo-class mostly does the same thing as our JavaScript-driven utility. However, it does not work well with Shadow DOM components as the element that receives focus is typically inside of the Shadow DOM, but we usually want to set the `:focus-visible` state on the host so we can style other parts of the component. Using other combinations such as `:has(:focus-visible)` does not work because `:has` does not pierce the Shadow DOM (as that would leak implementation details about the Shadow DOM contents). `:focus-within` does work with the Shadow DOM, but that has the same problem as `:focus` that was mentioned before. Unfortunately, a [`:focus-visible-within` pseudo-class does not exist yet](https://github.com/WICG/focus-visible/issues/151).
 
+> [!IMPORTANT]
 > Make sure the component has the correct [component structure](#component-structure) before continuing.
 
 #### JavaScript
@@ -234,7 +165,7 @@ The `ion-focusable` class needs to be set on an element that can be focused:
 ```jsx
 render() {
   return (
-    <Host class='ion-focusable'>
+    <Host class="ion-focusable">
       <slot></slot>
     </Host>
   );
@@ -269,7 +200,8 @@ Style the `ion-focused` class based on the spec for that element:
 }
 ```
 
-> Order is important! Focused should be after the activated and before the hover state.
+> [!IMPORTANT]
+> Order matters! Focused should be **before** the activated and hover states.
 
 
 #### User Customization
@@ -286,11 +218,12 @@ ion-button {
 
 ### Hover
 
-The [hover state](https://developer.mozilla.org/en-US/docs/Web/CSS/:hover) happens when a user moves their cursor on top of an element without pressing on it. It should not happen on mobile, only on desktop devices that support hover. 
+The [hover state](https://developer.mozilla.org/en-US/docs/Web/CSS/:hover) happens when a user moves their cursor on top of an element without pressing on it. It should not happen on mobile, only on desktop devices that support hover.
 
 > [!NOTE]
 > Some Android devices [incorrectly report their inputs](https://issues.chromium.org/issues/40855702) which can result in certain devices receiving hover events when they should not.
 
+> [!IMPORTANT]
 > Make sure the component has the correct [component structure](#component-structure) before continuing.
 
 #### CSS
@@ -321,7 +254,8 @@ Style the `:hover` based on the spec for that element:
 }
 ```
 
-> Order is important! Hover should be before the activated state.
+> [!IMPORTANT]
+> Order matters! Hover should be **before** the activated state.
 
 
 #### User Customization
@@ -336,6 +270,79 @@ ion-button {
 ```
 
 
+### Activated
+
+The activated state should be enabled for elements with actions on "press". It usually changes the opacity or background of an element.
+
+> [!WARNING]
+>`:active` should not be used here as it is not received on mobile Safari unless the element has a `touchstart` listener (which we don't necessarily want to have to add to every element). From [Safari Web Content Guide](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/AdjustingtheTextSize/AdjustingtheTextSize.html):
+>
+>> On iOS, mouse events are sent so quickly that the down or active state is never received. Therefore, the `:active` pseudo state is triggered only when there is a touch event set on the HTML element
+
+> [!IMPORTANT]
+> Make sure the component has the correct [component structure](#component-structure) before continuing.
+
+#### JavaScript
+
+The `ion-activatable` class needs to be set on an element that can be activated:
+
+```jsx
+render() {
+  return (
+    <Host class="ion-activatable">
+      <slot></slot>
+    </Host>
+  );
+}
+```
+
+Once that is done, the element will get the `ion-activated` class added on press after a small delay. This delay exists so that the active state does not show up when an activatable element is tapped while scrolling.
+
+In addition to setting that class, `ion-activatable-instant` can be set in order to have an instant press with no delay:
+
+```jsx
+<Host class="ion-activatable ion-activatable-instant">
+```
+
+#### CSS
+
+```css
+ /**
+   * @prop --color-activated: Color of the button when pressed
+   * @prop --background-activated: Background of the button when pressed
+   * @prop --background-activated-opacity: Opacity of the background when pressed
+   */
+```
+
+Style the `ion-activated` class based on the spec for that element:
+
+```scss
+:host(.ion-activated) .button-native {
+  color: var(--color-activated);
+
+  &::after {
+    background: var(--background-activated);
+
+    opacity: var(--background-activated-opacity);
+  }
+}
+```
+
+> [!IMPORTANT]
+> Order matters! Activated should be **after** the focused & hover states.
+
+#### User Customization
+
+Setting the activated state on the `::after` pseudo-element allows the user to customize the activated state without knowing what the default opacity is set at. A user can customize in the following ways to have a solid red background on press, or they can leave out `--background-activated-opacity` and the button will use the default activated opacity to match the spec.
+
+```css
+ion-button {
+  --background-activated: red;
+  --background-activated-opacity: 1;
+}
+```
+
+
 ### Ripple Effect
 
 The ripple effect should be added to elements for Material Design. It *requires* the `ion-activatable` class to be set on the parent element to work, and relative positioning on the parent.

.github/CONTRIBUTING.md

@@ -4,56 +4,53 @@ Thanks for your interest in contributing to the Ionic Framework! :tada:
 
 - [Contributing Etiquette](#contributing-etiquette)
 - [Creating an Issue](#creating-an-issue)
-  * [Creating a Good Code Reproduction](#creating-a-good-code-reproduction)
+  - [Creating a Good Code Reproduction](#creating-a-good-code-reproduction)
 - [Creating a Pull Request](#creating-a-pull-request)
-  * [Requirements](#requirements)
-  * [Setup](#setup)
-  * [Core](#core)
-    + [Modifying Components](#modifying-components)
-    + [Preview Changes](#preview-changes)
-    + [Lint Changes](#lint-changes)
-    + [Modifying Documentation](#modifying-documentation)
-    + [Modifying Tests](#modifying-tests)
+  - [Requirements](#requirements)
+  - [Setup](#setup)
+  - [Core](#core)
+    - [Modifying Components](#modifying-components)
+    - [Preview Changes](#preview-changes)
+    - [Lint Changes](#lint-changes)
+    - [Modifying Documentation](#modifying-documentation)
+    - [Modifying Tests](#modifying-tests)
       - [Screenshot Tests](#screenshot-tests)
-    + [Building Changes](#building-changes)
-  * [Angular, React, and Vue](#angular-react-and-vue)
-    + [Modifying Files](#modifying-files)
-    + [Preview Changes](#preview-changes-1)
-    + [Lint Changes](#lint-changes-1)
-    + [Modifying Tests](#modifying-tests-1)
-    + [Building Changes](#building-changes-1)
-  * [Submit Pull Request](#submit-pull-request)
+    - [Building Changes](#building-changes)
+  - [Angular, React, and Vue](#angular-react-and-vue)
+    - [Modifying Files](#modifying-files)
+    - [Preview Changes](#preview-changes-1)
+    - [Lint Changes](#lint-changes-1)
+    - [Modifying Tests](#modifying-tests-1)
+    - [Building Changes](#building-changes-1)
+  - [Submit Pull Request](#submit-pull-request)
 - [Commit Message Guidelines](#commit-message-guidelines)
-  * [Commit Message Format](#commit-message-format)
-  * [Revert](#revert)
-  * [Type](#type)
-  * [Scope](#scope)
-  * [Subject](#subject)
-  * [Body](#body)
-  * [Footer](#footer)
-  * [Examples](#examples)
+  - [Commit Message Format](#commit-message-format)
+  - [Revert](#revert)
+  - [Type](#type)
+  - [Scope](#scope)
+  - [Subject](#subject)
+  - [Body](#body)
+  - [Footer](#footer)
+  - [Examples](#examples)
 - [License](#license)
 
-
 ## Contributing Etiquette
 
 Please see our [Contributor Code of Conduct](https://github.com/ionic-team/ionic-framework/blob/main/CODE_OF_CONDUCT.md) for information on our rules of conduct.
 
-
 ## Creating an Issue
 
-* If you have a question about using the framework, please ask on the [Ionic Forum](http://forum.ionicframework.com/) or in the [Ionic Discord](https://ionic.link/discord).
+- If you have a question about using the framework, please ask on the [Ionic Forum](http://forum.ionicframework.com/) or in the [Ionic Discord](https://ionic.link/discord).
 
-* It is required that you clearly describe the steps necessary to reproduce the issue you are running into. Although we would love to help our users as much as possible, diagnosing issues without clear reproduction steps is extremely time-consuming and simply not sustainable.
+- It is required that you clearly describe the steps necessary to reproduce the issue you are running into. Although we would love to help our users as much as possible, diagnosing issues without clear reproduction steps is extremely time-consuming and simply not sustainable.
 
-* The issue list of this repository is exclusively for bug reports and feature requests. Non-conforming issues will be closed immediately.
+- The issue list of this repository is exclusively for bug reports and feature requests. Non-conforming issues will be closed immediately.
 
-* Issues with no clear steps to reproduce will not be triaged. If an issue is labeled with "needs: reply" and receives no further replies from the author of the issue for more than 14 days, it will be closed.
+- Issues with no clear steps to reproduce will not be triaged. If an issue is labeled with "needs: reply" and receives no further replies from the author of the issue for more than 14 days, it will be closed.
 
-* If you think you have found a bug, or have a new feature idea, please start by making sure it hasn't already been [reported](https://github.com/ionic-team/ionic-framework/issues?utf8=%E2%9C%93&q=is%3Aissue). You can search through existing issues to see if there is a similar one reported. Include closed issues as it may have been closed with a solution.
-
-* Next, [create a new issue](https://github.com/ionic-team/ionic-framework/issues/new/choose) that thoroughly explains the problem. Please fill out the populated issue form before submitting the issue.
+- If you think you have found a bug, or have a new feature idea, please start by making sure it hasn't already been [reported](https://github.com/ionic-team/ionic-framework/issues?utf8=%E2%9C%93&q=is%3Aissue). You can search through existing issues to see if there is a similar one reported. Include closed issues as it may have been closed with a solution.
 
+- Next, [create a new issue](https://github.com/ionic-team/ionic-framework/issues/new/choose) that thoroughly explains the problem. Please fill out the populated issue form before submitting the issue.
 
 ## Creating a Good Code Reproduction
 
@@ -69,42 +66,43 @@ Without a reliable code reproduction, it is unlikely we will be able to resolve
 
 ### How to Create a Reproduction
 
-* Create a new Ionic application using one of our starter templates. The `blank` starter application is a great choice for this. You can create one using the following Ionic CLI command: `ionic start myApp blank`
-* Add the minimum amount of code needed to recreate the issue you are experiencing. Do not include anything that is not required to reproduce the issue. This includes any 3rd party plugins you have installed.
-* Publish the application on GitHub and include a link to it when [creating an issue](#creating-an-issue).
-* Be sure to include steps to reproduce the issue. These steps should be clear and easy to follow.
+- Create a new Ionic application using one of our starter templates. The `blank` starter application is a great choice for this. You can create one using the following Ionic CLI command: `ionic start myApp blank`
+- Add the minimum amount of code needed to recreate the issue you are experiencing. Do not include anything that is not required to reproduce the issue. This includes any 3rd party plugins you have installed.
+- Publish the application on GitHub and include a link to it when [creating an issue](#creating-an-issue).
+- Be sure to include steps to reproduce the issue. These steps should be clear and easy to follow.
 
 ### Benefits of Creating a Reproduction
 
-* **Uses the latest version of Ionic:** By creating a new Ionic application, you are ensuring that you are testing against the latest version of the framework. Sometimes the issues you are experiencing have already been resolved in a newer version of the framework!
-* **Minimal surface area:** By removing code that is not needed in order to reproduce the issue, it makes it easier to identify the cause of the issue.
-* **No secret code needed:** Creating a minimal reproduction of the issue prevents you from having to publish any proprietary code used in your project.
-* **Get help fixing the issue:** If we can reliably reproduce an issue, there is a good chance we will be able to address it.
-
+- **Uses the latest version of Ionic:** By creating a new Ionic application, you are ensuring that you are testing against the latest version of the framework. Sometimes the issues you are experiencing have already been resolved in a newer version of the framework!
+- **Minimal surface area:** By removing code that is not needed in order to reproduce the issue, it makes it easier to identify the cause of the issue.
+- **No secret code needed:** Creating a minimal reproduction of the issue prevents you from having to publish any proprietary code used in your project.
+- **Get help fixing the issue:** If we can reliably reproduce an issue, there is a good chance we will be able to address it.
 
 ## Creating a Pull Request
 
 Before creating a pull request, please read our requirements that explains the minimal details to have your PR considered and merged into the codebase.
 
 ### Requirements
+
 1. PRs must reference an existing issue that describes the issue or feature being submitted.
 2. PRs must have a reproduction app or the issue must include a reproduction app to verify changes against.
 3. PRs must include tests covering the changed behavior or a description of why tests cannot be written.
 
 > Note: We appreciate you taking the time to contribute! Before submitting a pull request, please take the time to comment on the issue you are wanting to resolve. This helps us prevent duplicate effort or advise if the team is already addressing the issue.
 
-* Looking for an issue to fix? Look through our issues with the [help wanted](https://github.com/ionic-team/ionic-framework/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label!
+- Looking for an issue to fix? Look through our issues with the [help wanted](https://github.com/ionic-team/ionic-framework/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) label!
 
 ### Setup
 
-1. [Download the installer](https://nodejs.org/) for the LTS version of Node.js. This is the best way to also [install npm](https://blog.npmjs.org/post/85484771375/how-to-install-npm#_=_).
-2. Fork this repository.
-3. Clone your fork.
-4. Create a new branch from main for your change.
-5. Navigate into the directory of the package you wish to modify (core, angular, etc.).
-6. Run `npm install` to install dependencies for this package.
-7. Follow the steps for the specific package below.
-
+1. [Download the installer](https://nodejs.org/) for the LTS version of Node.js.
+2. Install pnpm following the [installation instructions](https://pnpm.io/installation).
+3. Fork this repository.
+4. Clone your fork.
+5. Create a new branch from main for your change.
+6. Navigate into the directory of the package you wish to modify (core, angular, etc.).
+7. Run `pnpm install` to install dependencies for this package.
+  - If you prefer to install all dependencies (core, angular, etc.) at once, run `pnpm -r install` from the root of the repository.
+8. Follow the steps for the specific package below.
 
 ### Core
 
@@ -120,12 +118,11 @@ Before creating a pull request, please read our requirements that explains the m
 8. After the build is finished, commit the changes. Please follow the [commit message format](#commit-message-format) for every commit.
 9. [Submit a Pull Request](#submit-pull-request) of your changes.
 
-
 #### Preview Changes
 
 ##### Previewing in this repository
 
-1. Run `npm start` from within the `core` directory.
+1. Run `pnpm start` from within the `core` directory.
 2. A browser should open at `http://localhost:3333/`.
 3. From here, navigate to one of the component's tests to preview your changes.
 4. If a test showing your change doesn't exist, [add a new test or update an existing one](#modifying-tests).
@@ -133,7 +130,7 @@ Before creating a pull request, please read our requirements that explains the m
 
 ##### Previewing in an external app
 
-We can use `npm pack` to test Ionic Framework changes in an external app outside of this repository. Follow the below steps based on your framework.
+We can use `pnpm pack` to test Ionic Framework changes in an external app outside of this repository. Follow the below steps based on your framework.
 
 ###### JavaScript
 
@@ -141,128 +138,112 @@ Run the following commands to build the core directory and pack the changes:
 
 ```bash
 cd core
-npm i
-npm run build
-npm pack --pack-destination ~
+pnpm install
+pnpm build
+pnpm pack --pack-destination ~
 ```
 
 Then, in your Ionic Framework JavaScript app, run the following command to use the built package with the `.tgz` file that was created:
 
 ```bash
-npm install file:/~/ionic-core-7.0.1.tgz
+pnpm install file:/~/ionic-core-7.0.1.tgz
 ```
 
-
 ###### Angular
 
 Run the following commands to build the core & angular directories and pack the changes:
 
 ```bash
 cd core
-npm i
-npm run build
-npm pack --pack-destination ~
+pnpm install
+pnpm build
+pnpm pack --pack-destination ~
 
 cd ../packages/angular
-npm i
-npm run sync
-npm run build
+pnpm build
 cd dist/
-npm pack --pack-destination ~
+pnpm pack --pack-destination ~
 ```
 
 Then, in your Ionic Framework Angular app, run the following commands to use the built packages with the `.tgz` files that were created:
 
 ```bash
 rm -rf .angular/
-npm install file:/~/ionic-core-7.0.1.tgz
-npm install file:/~/ionic-angular-7.0.1.tgz
+pnpm install file:/~/ionic-core-7.0.1.tgz
+pnpm install file:/~/ionic-angular-7.0.1.tgz
 ```
 
-
 ###### React
 
 Run the following commands to build the core & react directories and pack the changes:
 
 ```bash
 cd core
-npm i
-npm run build
-npm pack --pack-destination ~
+pnpm install
+pnpm build
+pnpm pack --pack-destination ~
 
 cd ../packages/react
-npm i
-npm run sync
-npm run build
-npm pack --pack-destination ~
+pnpm build
+pnpm pack --pack-destination ~
 
 cd ../react-router
-npm i
-npm run sync
-npm run build
-npm pack --pack-destination ~
+pnpm build
+pnpm pack --pack-destination ~
 ```
 
 Then, in your Ionic Framework React app, run the following commands to use the built packages with the `.tgz` files that were created:
 
 ```bash
-npm install file:/~/ionic-core-7.0.1.tgz
-npm install file:/~/ionic-react-7.0.1.tgz
-npm install file:/~/ionic-react-router-7.0.1.tgz
+pnpm install file:/~/ionic-core-7.0.1.tgz
+pnpm install file:/~/ionic-react-7.0.1.tgz
+pnpm install file:/~/ionic-react-router-7.0.1.tgz
 ```
 
-
 ##### Vue
 
 Run the following commands to build the core & vue directories and pack the changes:
 
 ```bash
 cd core
-npm i
-npm run build
-npm pack --pack-destination ~
+pnpm install
+pnpm build
+pnpm pack --pack-destination ~
 
 cd ../packages/vue
-npm i
-npm run sync
-npm run build
-npm pack --pack-destination ~
+pnpm build
+pnpm pack --pack-destination ~
 
 cd ../vue-router
-npm i
-npm run sync
-npm run build
-npm pack --pack-destination ~
+pnpm build
+pnpm pack --pack-destination ~
 ```
 
 Then, in your Ionic Framework Vue app, run the following commands to use the built packages with the `.tgz` files that were created:
 
 ```bash
-npm install file:/~/ionic-core-7.0.1.tgz
-npm install file:/~/ionic-vue-7.0.1.tgz
-npm install file:/~/ionic-vue-router-7.0.1.tgz
+pnpm install file:/~/ionic-core-7.0.1.tgz
+pnpm install file:/~/ionic-vue-7.0.1.tgz
+pnpm install file:/~/ionic-vue-router-7.0.1.tgz
 ```
 
-
 #### Lint Changes
 
-1. Run `npm run lint` to lint the TypeScript and Sass.
-2. If there are lint errors, run `npm run lint.fix` to automatically fix any errors. Repeat step 1 to ensure the errors have been fixed, and manually fix them if not.
-3. To lint and fix only TypeScript errors, run `npm run lint.ts` and `npm run lint.ts.fix`, respectively.
-4. To lint and fix only Sass errors, run `npm run lint.sass` and `npm run lint.sass.fix`, respectively.
-
+1. Run `pnpm lint` to lint the TypeScript and Sass.
+2. If there are lint errors, run `pnpm lint.fix` to automatically fix any errors. Repeat step 1 to ensure the errors have been fixed, and manually fix them if not.
+3. To lint and fix only TypeScript errors, run `pnpm lint.ts` and `pnpm lint.ts.fix`, respectively.
+4. To lint and fix only Sass errors, run `pnpm lint.sass` and `pnpm lint.sass.fix`, respectively.
 
 #### Modifying Documentation
 
 - Changes to manually written documentation should be made in the `ionic-docs` repo: https://github.com/ionic-team/ionic-docs/tree/main/docs
   - In your `ionic-docs` PR, please add a link back to the related `ionic-framework` PR.
 - Changes to auto generated documentation should be made in the `ionic-framework` repo. These can be done in the same PR as your fix or feature.
-  - Run `npm run build` and commit all updates to ensure your changes make it into the generated documentation.
+  - Run `pnpm build` and commit all updates to ensure your changes make it into the generated documentation.
   - `Usage`: update the component's usage examples in the component's `usage/` directory.
   - `Properties`, `Events`, or `Methods`: update the component's TypeScript file (`*.tsx`).
   - `CSS Custom Properties`: update the component's main Sass file (`*.scss`).
 
-
 #### Modifying Tests
 
 1. Locate the test to modify inside the `test/` folder in the component's directory.
@@ -277,43 +258,47 @@ See [Ionic's E2E testing guide](../core/src/utils/test/playwright/docs/README.md
 1. If the test exists in screenshot, there will be a file named `e2e.ts` in the directory of the test.
 2. A screenshot test can be added by including this file and adding one or more `test()` calls that include a call to `page.compareScreenshot()`. See [Stencil end-to-end testing](https://stenciljs.com/docs/end-to-end-testing) and existing tests in `core/` for examples.
 3. **Important:** each `test()` should have only one screenshot (`page.compareScreenshot()`) call **or** it should check the expect at the end of each test. If there is a mismatch it will fail the test which will prevent the rest of the test from running, i.e. if the first screenshot fails the remaining screenshot calls would not be called _unless_ they are in a separate test or all of the expects are called at the end.
-4. To run screenshot locally, use the following command: `npm run test.screenshot`.
-    - To run screenshot for a specific test, pass the path to the test or a string to search for.
-    - For example, running all `alert` tests: `npm run test.screenshot alert`.
-    - Or, running the basic `alert` tests: `npm run test.screenshot src/components/alert/test/basic/e2e.ts`.
-
+4. To run screenshot locally, use the following command: `pnpm test.e2e`.
+   - To run screenshot for a specific test, pass the path to the test or a string to search for.
+   - For example, running all `alert` tests: `pnpm test.e2e alert`.
+   - Or, running the basic `alert` tests: `pnpm test.e2e src/components/alert/test/basic/e2e.ts`.
 
 #### Building Changes
 
-1. Once all changes have been made and the documentation has been updated, run `npm run build` inside of the `core` directory. This will add your changes to any auto-generated files, if necessary.
+1. Once all changes have been made and the documentation has been updated, run `pnpm build` inside of the `core` directory. This will add your changes to any auto-generated files, if necessary.
 2. Review the changes and, if everything looks correct, [commit](#commit-message-format) the changes.
 3. Make sure the build has finished before committing. If you made changes to the documentation, properties, methods, or anything else that requires an update to a generate file, this needs to be committed.
 4. After the changes have been pushed, publish the branch and [create a pull request](#creating-a-pull-request).
 
+> [!WARNING]
+> If you are receiving errors about missing packages, you may need to run `pnpm install --force` to force the installation of the missing packages.
+
 ### Angular, React, and Vue
 
 #### Modifying Files
 
 1. Locate the files inside the relevant root directory:
-  - Angular: [`/packages/angular/src`](/packages/angular/src)
-  - React: [`/packages/react/src`](/packages/react/src)
-  - Vue: [`/packages/vue/src`](/packages/vue/src)
+
+- Angular: [`/packages/angular/src`](/packages/angular/src)
+- React: [`/packages/react/src`](/packages/react/src)
+- Vue: [`/packages/vue/src`](/packages/vue/src)
+
 2. Make your changes to the files. If the change is overly complex or out of the ordinary, add comments so we can understand the changes.
 3. Run lint on the directory and make sure there are no errors.
-4. Build the project.
+4. Build the project with `pnpm build`.
+  - If you prefer to build all packages (core, angular, etc.) at once, run `pnpm -r build` from the root of the repository.
 5. After the build is finished, commit the changes. Please follow the [commit message format](#commit-message-format) for every commit.
 6. [Submit a Pull Request](#submit-pull-request) of your changes.
 
-
-
 #### Preview Changes
 
 ##### Previewing in this repository
 
 Follow the steps in the test directory for each framework:
-  - Angular: [`/packages/angular/test`](/packages/angular/test/README.md)
-  - React: [`/packages/react/test`](/packages/react/test/README.md)
-  - Vue: [`/packages/vue/test`](/packages/vue/test/README.md)
+
+- Angular: [`/packages/angular/test`](/packages/angular/test/README.md)
+- React: [`/packages/react/test`](/packages/react/test/README.md)
+- Vue: [`/packages/vue/test`](/packages/vue/test/README.md)
 
 ##### Previewing in an external app
 
@@ -321,25 +306,29 @@ Follow the steps to [preview changes in core](#preview-changes).
 
 #### Lint Changes
 
-1. Run `npm run lint` to lint the TypeScript in the relevant directory:
-  - Angular: [`/packages/angular/src`](/packages/angular/src)
-  - React: [`/packages/react/src`](/packages/react/src)
-  - Vue: [`/packages/vue/src`](/packages/vue/src)
-2. If there are lint errors, run `npm run lint.fix` to automatically fix any errors. Repeat step 1 to ensure the errors have been fixed, and manually fix them if not.
+1. Run `pnpm lint` to lint the TypeScript in the relevant directory:
+
+- Angular: [`/packages/angular/src`](/packages/angular/src)
+- React: [`/packages/react/src`](/packages/react/src)
+- Vue: [`/packages/vue/src`](/packages/vue/src)
+
+2. If there are lint errors, run `pnpm lint.fix` to automatically fix any errors. Repeat step 1 to ensure the errors have been fixed, and manually fix them if not.
 
 #### Modifying Tests
 
 1. Locate the e2e test to modify inside the relevant test app directory:
-  - Angular: [`/packages/angular/test/base/e2e/src`](/packages/angular/test/base/e2e/src)
-  - React: [`/packages/react/test/base/tests/e2e/specs`](/packages/react/test/base/tests/e2e/specs)
-  - Vue: [`/packages/vue/test/base/tests/e2e/specs`](/packages/vue/test/base/tests/e2e/specs)
+
+- Angular: [`/packages/angular/test/base/e2e/src`](/packages/angular/test/base/e2e/src)
+- React: [`/packages/react/test/base/tests/e2e/specs`](/packages/react/test/base/tests/e2e/specs)
+- Vue: [`/packages/vue/test/base/tests/e2e/specs`](/packages/vue/test/base/tests/e2e/specs)
+
 2. If a test exists, modify the test by adding an example to reproduce the problem fixed or feature added.
 3. If a new test is needed, copy an existing test, rename it, and edit the content in the test file.
-4. Run `npm run test` to run your tests.
+4. Run `pnpm test` to run your tests.
 
 #### Building Changes
 
-1. Once all changes have been made, run `npm run build` inside of the package's root directory. This will add your changes to any auto-generated files, if necessary.
+1. Once all changes have been made, run `pnpm build` inside of the package's root directory. This will add your changes to any auto-generated files, if necessary.
 2. Review the changes and, if everything looks correct, [commit](#commit-message-format) the changes.
 3. Make sure the build has finished before committing. If you made changes to the documentation, properties, methods, or anything else that requires an update to a generate file, this needs to be committed.
 4. After the changes have been pushed, publish the branch and [create a pull request](#creating-a-pull-request).
@@ -356,14 +345,13 @@ The team has an internal design process for new Ionic features, which must be co
 
 To expedite the process, please ensure that all feature PRs have an associated issue created, with a clear use case for why the feature should be added to Ionic.
 
-
 ## Commit Message Guidelines
 
 We have very precise rules over how our git commit messages should be formatted. This leads to readable messages that are easy to follow when looking through the project history. We also use the git commit messages to generate our [changelog](https://github.com/ionic-team/ionic-framework/blob/main/CHANGELOG.md). Our format closely resembles Angular's [commit message guidelines](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit).
 
 ### Commit Message Format
 
-We follow the [Conventional Commits specification](https://www.conventionalcommits.org/). A commit message consists of a **header**, **body** and **footer**.  The header has a **type**, **scope** and **subject**:
+We follow the [Conventional Commits specification](https://www.conventionalcommits.org/). A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
 
 ```
 <type>(<scope>): <subject>
@@ -385,14 +373,14 @@ If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. Howev
 
 Must be one of the following:
 
-* **feat**: A new feature
-* **fix**: A bug fix
-* **docs**: Documentation only changes
-* **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
-* **refactor**: A code change that neither fixes a bug nor adds a feature
-* **perf**: A code change that improves performance
-* **test**: Adding missing tests
-* **chore**: Changes to the build process or auxiliary tools and libraries such as documentation generation
+- **feat**: A new feature
+- **fix**: A bug fix
+- **docs**: Documentation only changes
+- **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+- **refactor**: A code change that neither fixes a bug nor adds a feature
+- **perf**: A code change that improves performance
+- **test**: Adding missing tests
+- **chore**: Changes to the build process or auxiliary tools and libraries such as documentation generation
 
 ### Scope
 
@@ -402,12 +390,12 @@ The scope can be anything specifying place of the commit change. Usually it will
 
 The subject contains succinct description of the change:
 
-* use the imperative, present tense: "change" not "changed" nor "changes"
-* do not capitalize first letter
-* do not place a period `.` at the end
-* entire length of the commit message must not go over 50 characters
-* describe what the commit does, not what issue it relates to or fixes
-* **be brief, yet descriptive** - we should have a good understanding of what the commit does by reading the subject
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- do not capitalize first letter
+- do not place a period `.` at the end
+- entire length of the commit message must not go over 50 characters
+- describe what the commit does, not what issue it relates to or fixes
+- **be brief, yet descriptive** - we should have a good understanding of what the commit does by reading the subject
 
 ### Body
 
@@ -469,7 +457,6 @@ revert: feat(skeleton-text): add animated property
 This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
 ```
 
-
 ## License
 
 By contributing your code to the ionic-team/ionic GitHub Repository, you agree to license your contribution under the MIT license.

.github/workflows/actions/build-angular-server/action.yml

@@ -6,13 +6,20 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
-
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
+    - uses: ./.github/workflows/actions/download-archive
+      with:
+        name: ionic-core
+        path: ./core
+        filename: CoreBuild.zip
     - name: Install Angular Server Dependencies
-      run: npm ci
+      run: pnpm install
       shell: bash
       working-directory: ./packages/angular-server
     - name: Build
-      run: npm run build.prod
+      run: pnpm run build.prod
       shell: bash
       working-directory: ./packages/angular-server
     - uses: ./.github/workflows/actions/upload-archive

.github/workflows/actions/build-angular/action.yml

@@ -6,25 +6,24 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
         path: ./core
         filename: CoreBuild.zip
     - name: Install Angular Dependencies
-      run: npm ci
-      shell: bash
-      working-directory: ./packages/angular
-    - name: Sync
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/angular
     - name: Lint
-      run: npm run lint
+      run: pnpm run lint
       shell: bash
       working-directory: ./packages/angular
     - name: Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ./packages/angular
     - name: Check Diff

.github/workflows/actions/build-core-stencil-prerelease/action.yml

@@ -12,17 +12,19 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
-
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - name: Install Dependencies
-      run: npm ci
+      run: pnpm install
       working-directory: ./core
       shell: bash
     - name: Install Stencil ${{ inputs.stencil-version }}
       working-directory: ./core
-      run: npm i @stencil/core@${{ inputs.stencil-version }}
+      run: pnpm i @stencil/core@${{ inputs.stencil-version }}
       shell: bash
     - name: Build Core
-      run: npm run build -- --ci --debug --verbose
+      run: pnpm npm run build -- --ci --debug --verbose
       working-directory: ./core
       shell: bash
     - uses: ./.github/workflows/actions/upload-archive

.github/workflows/actions/build-core/action.yml

@@ -12,19 +12,22 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - name: Install Dependencies
-      run: npm install
+      run: pnpm install
       working-directory: ./core
       shell: bash
     # If an Ionicons version was specified install that.
     # Otherwise just use the version defined in the package.json.
     - name: Install Ionicons Version
       if: inputs.ionicons-version != ''
-      run: npm install ionicons@${{ inputs.ionicons-version }}
+      run: pnpm install ionicons@${{ inputs.ionicons-version }}
       working-directory: ./core
       shell: bash
     - name: Build Core
-      run: npm run build -- --ci
+      run: pnpm run build --ci
       working-directory: ./core
       shell: bash
     - uses: ./.github/workflows/actions/upload-archive

.github/workflows/actions/build-react-router/action.yml

@@ -6,6 +6,9 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
@@ -17,19 +20,15 @@ runs:
         path: ./packages/react
         filename: ReactBuild.zip
     - name: Install Dependencies
-      run: npm ci
-      shell: bash
-      working-directory: ./packages/react-router
-    - name: Sync
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/react-router
     - name: Lint
-      run: npm run lint
+      run: pnpm run lint
       shell: bash
       working-directory: ./packages/react-router
     - name: Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ./packages/react-router
     - uses: ./.github/workflows/actions/upload-archive

.github/workflows/actions/build-react/action.yml

@@ -6,29 +6,28 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
         path: ./core
         filename: CoreBuild.zip
     - name: Install React Dependencies
-      run: npm ci
-      shell: bash
-      working-directory: ./packages/react
-    - name: Sync
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/react
     - name: Lint
-      run: npm run lint
+      run: pnpm run lint
       shell: bash
       working-directory: ./packages/react
     - name: Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ./packages/react
     - name: Test Spec
-      run: npm run test.spec
+      run: pnpm run test.spec
       shell: bash
       working-directory: ./packages/react
     - name: Check Diff

.github/workflows/actions/build-vue-router/action.yml

@@ -6,6 +6,9 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
@@ -17,23 +20,19 @@ runs:
         path: ./packages/vue
         filename: VueBuild.zip
     - name: Install Vue Router Dependencies
-      run: npm ci
-      shell: bash
-      working-directory: ./packages/vue-router
-    - name: Sync
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/vue-router
     - name: Lint
-      run: npm run lint
+      run: pnpm run lint
       shell: bash
       working-directory: ./packages/vue-router
     - name: Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ./packages/vue-router
     - name: Test Spec
-      run: npm run test.spec
+      run: pnpm run test.spec
       shell: bash
       working-directory: ./packages/vue-router
     - uses: ./.github/workflows/actions/upload-archive

.github/workflows/actions/build-vue/action.yml

@@ -6,25 +6,24 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
         path: ./core
         filename: CoreBuild.zip
     - name: Install Vue Dependencies
-      run: npm ci
-      shell: bash
-      working-directory: ./packages/vue
-    - name: Sync
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/vue
     - name: Lint
-      run: npm run lint
+      run: pnpm run lint
       shell: bash
       working-directory: ./packages/vue
     - name: Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ./packages/vue
     - name: Check Diff

.github/workflows/actions/publish-npm/action.yml

@@ -22,6 +22,9 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     # Provenance requires npm 9.5.0+
     - name: Install latest npm
       run: npm install -g npm@latest
@@ -29,27 +32,26 @@ runs:
     # This ensures the local version of Lerna is installed
     # and that we do not use the global Lerna version
     - name: Install root dependencies
-      run: npm ci
+      run: pnpm install
       shell: bash
-    - name: Install Dependencies
-      run: npx lerna bootstrap --include-dependencies --scope ${{ inputs.scope }} --ignore-scripts -- --legacy-peer-deps
+    - name: Install project dependencies
+      run: pnpm install
       shell: bash
       working-directory: ${{ inputs.working-directory }}
     - name: Update Version
-      run: npx lerna version ${{ inputs.version }} --yes --exact --no-changelog --no-push --no-git-tag-version --preid=${{ inputs.preid }}
+      run: pnpm exec lerna version ${{ inputs.version }} --yes --exact --no-changelog --no-push --no-git-tag-version --preid=${{ inputs.preid }}
       shell: bash
       working-directory: ${{ inputs.working-directory }}
     - name: Run Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ${{ inputs.working-directory }}
     - name: Prepare NPM Token
-      run: echo //registry.npmjs.org/:_authToken=${NPM_TOKEN} > .npmrc
-      working-directory: ${{ inputs.working-directory }}
+      run: pnpm config set //registry.npmjs.org/:_authToken ${NPM_TOKEN}
       shell: bash
       env:
         NPM_TOKEN: ${{ inputs.token }}
     - name: Publish to NPM
-      run: npm publish ${{ inputs.folder }} --tag ${{ inputs.tag }} --provenance
+      run: pnpm publish ${{ inputs.folder }} --tag ${{ inputs.tag }} --provenance --no-git-checks
       shell: bash
       working-directory: ${{ inputs.working-directory }}

.github/workflows/actions/test-angular-e2e/action.yml

@@ -9,6 +9,9 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
@@ -29,14 +32,10 @@ runs:
       shell: bash
       working-directory: ./packages/angular/test
     - name: Install Dependencies
-      run: npm install
-      shell: bash
-      working-directory: ./packages/angular/test/build/${{ inputs.app }}
-    - name: Sync Built Changes
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/angular/test/build/${{ inputs.app }}
     - name: Run Tests
-      run: npm run test
+      run: pnpm run test
       shell: bash
       working-directory: ./packages/angular/test/build/${{ inputs.app }}

.github/workflows/actions/test-core-lint/action.yml

@@ -6,12 +6,15 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - name: Install Dependencies
-      run: npm ci
+      run: pnpm install
       working-directory: ./core
       shell: bash
     - name: Lint
-      run: npm run lint
+      run: pnpm run lint
       shell: bash
       working-directory: ./core
     # Lint changes should be pushed

.github/workflows/actions/test-core-screenshot/action.yml

@@ -16,38 +16,21 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
         path: ./core
         filename: CoreBuild.zip
-    - name: Install Playwright Dependencies
-      run: npm install && npx playwright install && npx playwright install-deps
+    - name: Install Dependencies
+      run: pnpm install
       shell: bash
       working-directory: ./core
-    - id: clean-component-name
-      name: Clean Component Name
-      # Remove `ion-` prefix from the `component` variable if it exists.
-      run: |
-        echo "component=$(echo ${{ inputs.component }} | sed 's/ion-//g')" >> $GITHUB_OUTPUT
-      shell: bash
-    - id: set-test-file
-      name: Set Test File
-      # Screenshots can be updated for all components or specified component(s).
-      # If the `component` variable is set, then the test has the option to
-      # - run all the file paths that are in a component folder.
-      # -- For example: if the `component` value is "item", then the test will run all the file paths that are in the "src/components/item" folder.
-      # -- For example: if the `component` value is "item chip", then the test will run all the file paths that are in the "src/components/item" and "src/components/chip" folders.
-      run: |
-        if [ -n "${{ steps.clean-component-name.outputs.component }}" ]; then
-          echo "testFile=\$(echo '${{ steps.clean-component-name.outputs.component }}' | awk '{for(i=1;i<=NF;i++) \$i=\"src/components/\"\$i}1')" >> $GITHUB_OUTPUT
-        else
-          echo "testFile=$(echo '')" >> $GITHUB_OUTPUT
-        fi
-      shell: bash
     - name: Test
       if: inputs.update != 'true'
-      run: npm run test.e2e ${{ steps.set-test-file.outputs.testFile }} -- --shard=${{ inputs.shard }}/${{ inputs.totalShards }}
+      run: pnpm run test.e2e.docker.ci ${{ inputs.component }} -- --shard=${{ inputs.shard }}/${{ inputs.totalShards }}
       shell: bash
       working-directory: ./core
     - name: Test and Update
@@ -69,7 +52,7 @@ runs:
       # which is why we not using the upload-archive
       # composite step here.
       run: |
-        npm run test.e2e ${{ steps.set-test-file.outputs.testFile }} -- --shard=${{ inputs.shard }}/${{ inputs.totalShards }} --update-snapshots
+        pnpm run test.e2e.docker.ci ${{ inputs.component }} -- --shard=${{ inputs.shard }}/${{ inputs.totalShards }} --update-snapshots
         git add src/\*.png --force
         mkdir updated-screenshots
         cd ../ && rsync -R --progress $(git diff --name-only --cached) core/updated-screenshots

.github/workflows/actions/test-core-spec/action.yml

@@ -9,12 +9,15 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - name: Install Dependencies
-      run: npm ci
+      run: pnpm install
       working-directory: ./core
       shell: bash
     - name: Install Stencil ${{ inputs.stencil-version }}
-      run: npm install @stencil/core@${{ inputs.stencil-version }}
+      run: pnpm install @stencil/core@${{ inputs.stencil-version }}
       shell: bash
       working-directory: ./core
       if: ${{ inputs.stencil-version != '' }}
@@ -24,6 +27,6 @@ runs:
         path: ./core
         filename: CoreBuild.zip
     - name: Test
-      run: npm run test.spec -- --ci
+      run: pnpm run test.spec --ci
       shell: bash
       working-directory: ./core

.github/workflows/actions/test-react-e2e/action.yml

@@ -9,6 +9,9 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
@@ -29,19 +32,15 @@ runs:
       shell: bash
       working-directory: ./packages/react/test
     - name: Install Dependencies
-      run: npm install
-      shell: bash
-      working-directory: ./packages/react/test/build/${{ inputs.app }}
-    - name: Sync Built Changes
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/react/test/build/${{ inputs.app }}
     - name: Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ./packages/react/test/build/${{ inputs.app }}
     - name: Run Tests
-      run: npm run e2e
+      run: pnpm run e2e
       shell: bash
       working-directory: ./packages/react/test/build/${{ inputs.app }}
 

.github/workflows/actions/test-react-router-e2e/action.yml

@@ -9,6 +9,9 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
@@ -29,18 +32,14 @@ runs:
       shell: bash
       working-directory: ./packages/react-router/test
     - name: Install Dependencies
-      run: npm install
-      shell: bash
-      working-directory: ./packages/react-router/test/build/${{ inputs.app }}
-    - name: Sync Built Changes
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/react-router/test/build/${{ inputs.app }}
     - name: Build
-      run: npm run build
+      run: pnpm run build
       shell: bash
       working-directory: ./packages/react-router/test/build/${{ inputs.app }}
     - name: Run Tests
-      run: npm run e2e
+      run: pnpm run e2e
       shell: bash
       working-directory: ./packages/react-router/test/build/${{ inputs.app }}

.github/workflows/actions/test-vue-e2e/action.yml

@@ -9,6 +9,9 @@ runs:
     - uses: actions/setup-node@v4
       with:
         node-version: 18.x
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - uses: ./.github/workflows/actions/download-archive
       with:
         name: ionic-core
@@ -29,18 +32,14 @@ runs:
       shell: bash
       working-directory: ./packages/vue/test
     - name: Install Dependencies
-      run: npm install
-      shell: bash
-      working-directory: ./packages/vue/test/build/${{ inputs.app }}
-    - name: Sync
-      run: npm run sync
+      run: pnpm install
       shell: bash
       working-directory: ./packages/vue/test/build/${{ inputs.app }}
     - name: Run Spec Tests
-      run: npm run test:unit
+      run: pnpm run test:unit
       shell: bash
       working-directory: ./packages/vue/test/build/${{ inputs.app }}
     - name: Run E2E Tests
-      run: npm run test:e2e
+      run: pnpm run test:e2e
       shell: bash
       working-directory: ./packages/vue/test/build/${{ inputs.app }}

.github/workflows/actions/update-reference-screenshots/action.yml

@@ -25,12 +25,9 @@ runs:
       # Configure user as Ionitron
       # and push only the changed .png snapshots
       # to the remote branch.
-      # Screenshots are in .gitignore
+      # Non-Linux screenshots are in .gitignore
       # to prevent local screenshots from getting
-      # pushed to Git. As a result, we need --force
-      # here so that CI generated screenshots can
-      # get added to git. Screenshot ground truths
-      # should only be added via this CI process.
+      # pushed to Git.
       run: |
         git config user.name ionitron
         git config user.email hi@ionicframework.com
@@ -38,7 +35,7 @@ runs:
         # This adds an empty entry for new
         # screenshot files so we can track them with
         # git diff
-        git add src/\*.png --force -N
+        git add src/\*.png -N
 
         if git diff --exit-code; then
           echo -e "\033[1;31m⚠️ Error: No new screenshots generated ⚠️\033[0m"
@@ -48,7 +45,7 @@ runs:
         else
           # This actually adds the contents
           # of the screenshots (including new ones)
-          git add src/\*.png --force
+          git add src/\*.png
           git commit -m "chore(): add updated snapshots"
           git push
         fi

.github/workflows/dev-build.yml

@@ -10,11 +10,14 @@ jobs:
       dev-hash: ${{ steps.create-dev-hash.outputs.DEV_HASH }}
     steps:
       - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v2
+        with:
+          version: 8
       # A 1 is required before the timestamp
       # as lerna will fail when there is a leading 0
       # See https://github.com/lerna/lerna/issues/2840
       - name: Install Dependencies
-        run: npm ci
+        run: pnpm install
         shell: bash
       - id: create-dev-hash
         name: Create Dev Hash

.github/workflows/nightly.yml

@@ -13,11 +13,14 @@ jobs:
       nightly-hash: ${{ steps.create-nightly-hash.outputs.NIGHTLY_HASH }}
     steps:
       - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v2
+        with:
+          version: 8
       # A 1 is required before the timestamp
       # as lerna will fail when there is a leading 0
       # See https://github.com/lerna/lerna/issues/2840
       - name: Install Dependencies
-        run: npm ci
+        run: pnpm install
         shell: bash
       - id: create-nightly-hash
         name: Create Nightly Hash

.github/workflows/release-ionic.yml

@@ -161,7 +161,6 @@ jobs:
         version: ${{ inputs.version }}
         preid: ${{ inputs.preid }}
         working-directory: 'packages/angular-server'
-        folder: './dist'
         token: ${{ secrets.NPM_TOKEN }}
 
   release-react-router:

.github/workflows/release.yml

@@ -54,6 +54,9 @@ jobs:
       with:
         token: ${{ secrets.IONITRON_TOKEN }}
         fetch-depth: 0
+    - uses: pnpm/action-setup@v2
+      with:
+        version: 8
     - name: Configure Identity
       # Commits from github-actions do not
       # trigger other GitHub Actions. As a result,
@@ -101,7 +104,7 @@ jobs:
       # so we do that here.
       - name: Bump Package Lock
         run: |
-          lerna exec "npm install --package-lock-only"
+          pnpm install --lockfile-only
           git add .
           git commit -m "chore(): update package lock files"
           git push

.github/workflows/update-screenshots.yml

@@ -3,6 +3,20 @@ name: 'Update Reference Screenshots'
 on:
   workflow_dispatch:
     inputs:
+      # Screenshots can be updated for all components or specified component(s).
+      # If the `component` variable is set, then the test has the option to
+      # - run all the instances of the specified component(s) in the `src/components` folder
+      # -- For example: if the `component` value is "item", then the following command will be: `npm run test.e2e item`
+      # - run the specified file path
+      # -- For example: if the `component` value is "src/components/item/test/basic", then the following command will be: `npm run test.e2e src/components/item/test/basic`
+      # - run multiple specified components based on the space-separated value
+      # -- For example: if the `component` value is "item basic", then the following command will be: `npm run test.e2e item basic`
+      # -- For example: if the `component` value is "src/components/item/test/basic src/components/item/test/a11y", then the following command will be: `npm run test.e2e src/components/item/test/basic src/components/item/test/a11y`
+      #
+      # If the `component` variable is not set, then the test will run all the instances of the components in the `src/components` folder.
+      # - For example: `npm run test.e2e`
+      #
+      # More common options can be found at the Playwright Command line page: https://playwright.dev/docs/test-cli
       component:
         description: 'What component(s) should be updated? (leave blank to update all or use a space-separated list for multiple components)'
         required: false

.gitignore

@@ -68,7 +68,16 @@ core/www/
 # playwright
 core/test-results/
 core/playwright-report/
-core/**/*-snapshots
+
+# ground truths generated outside of docker should not be committed to the repo
+core/**/*-snapshots/*
+
+# new ground truths should only be generated inside of docker which will result in -linux.png screenshots
+!core/**/*-snapshots/*-linux.png
+
+# these files are going to be different per-developer environment so do not add them to the repo
+core/docker-display.txt
+core/docker-display-volume.txt
 
 # angular
 packages/angular/css/

CHANGELOG.md

@@ -3,6 +3,35 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [7.8.2](https://github.com/ionic-team/ionic-framework/compare/v7.8.1...v7.8.2) (2024-03-27)
+
+
+### Bug Fixes
+
+* **searchbar:** autocapitalize is initialized correctly ([#29197](https://github.com/ionic-team/ionic-framework/issues/29197)) ([8ad66c0](https://github.com/ionic-team/ionic-framework/commit/8ad66c03d777edcab19c97cba696b171acc2d2e8)), closes [#29193](https://github.com/ionic-team/ionic-framework/issues/29193)
+
+
+
+
+
+## [7.8.1](https://github.com/ionic-team/ionic-framework/compare/v7.8.0...v7.8.1) (2024-03-20)
+
+
+### Bug Fixes
+
+* **datetime:** wheel picker shows consistently in overlays ([#29147](https://github.com/ionic-team/ionic-framework/issues/29147)) ([19c1bc1](https://github.com/ionic-team/ionic-framework/commit/19c1bc16cbc6725463890382365203824b7fd353)), closes [#26234](https://github.com/ionic-team/ionic-framework/issues/26234)
+* **header:** iOS headers in MD app are not hidden ([#29164](https://github.com/ionic-team/ionic-framework/issues/29164)) ([fdfecd3](https://github.com/ionic-team/ionic-framework/commit/fdfecd32c33c41cf202d3b30c073bfb1b077e2d6)), closes [#28867](https://github.com/ionic-team/ionic-framework/issues/28867)
+* **react:** avoid definitely typed errors with @types/react@18 ([#29182](https://github.com/ionic-team/ionic-framework/issues/29182)) ([58d217d](https://github.com/ionic-team/ionic-framework/commit/58d217d0cf6b716da855c71c169fb1870d4067d3)), closes [#29178](https://github.com/ionic-team/ionic-framework/issues/29178)
+
+
+### Performance Improvements
+
+* **datetime:** calendar body shows immediately in modal on ios ([#29163](https://github.com/ionic-team/ionic-framework/issues/29163)) ([f759776](https://github.com/ionic-team/ionic-framework/commit/f75977699dae5aeea3d97d4318377633e935afb9)), closes [#24542](https://github.com/ionic-team/ionic-framework/issues/24542)
+
+
+
+
+
 # [7.8.0](https://github.com/ionic-team/ionic-framework/compare/v7.7.5...v7.8.0) (2024-03-13)
 
 

core/CHANGELOG.md

@@ -3,6 +3,34 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [7.8.2](https://github.com/ionic-team/ionic-framework/compare/v7.8.1...v7.8.2) (2024-03-27)
+
+
+### Bug Fixes
+
+* **searchbar:** autocapitalize is initialized correctly ([#29197](https://github.com/ionic-team/ionic-framework/issues/29197)) ([8ad66c0](https://github.com/ionic-team/ionic-framework/commit/8ad66c03d777edcab19c97cba696b171acc2d2e8)), closes [#29193](https://github.com/ionic-team/ionic-framework/issues/29193)
+
+
+
+
+
+## [7.8.1](https://github.com/ionic-team/ionic-framework/compare/v7.8.0...v7.8.1) (2024-03-20)
+
+
+### Bug Fixes
+
+* **datetime:** wheel picker shows consistently in overlays ([#29147](https://github.com/ionic-team/ionic-framework/issues/29147)) ([19c1bc1](https://github.com/ionic-team/ionic-framework/commit/19c1bc16cbc6725463890382365203824b7fd353)), closes [#26234](https://github.com/ionic-team/ionic-framework/issues/26234)
+* **header:** iOS headers in MD app are not hidden ([#29164](https://github.com/ionic-team/ionic-framework/issues/29164)) ([fdfecd3](https://github.com/ionic-team/ionic-framework/commit/fdfecd32c33c41cf202d3b30c073bfb1b077e2d6)), closes [#28867](https://github.com/ionic-team/ionic-framework/issues/28867)
+
+
+### Performance Improvements
+
+* **datetime:** calendar body shows immediately in modal on ios ([#29163](https://github.com/ionic-team/ionic-framework/issues/29163)) ([f759776](https://github.com/ionic-team/ionic-framework/commit/f75977699dae5aeea3d97d4318377633e935afb9)), closes [#24542](https://github.com/ionic-team/ionic-framework/issues/24542)
+
+
+
+
+
 # [7.8.0](https://github.com/ionic-team/ionic-framework/compare/v7.7.5...v7.8.0) (2024-03-13)
 
 

core/Dockerfile

@@ -0,0 +1,5 @@
+# Get Playwright
+FROM mcr.microsoft.com/playwright:v1.42.1
+
+# Set the working directory
+WORKDIR /ionic

core/api.txt

@@ -1158,7 +1158,7 @@ ion-row,shadow
 
 ion-searchbar,scoped
 ion-searchbar,prop,animated,boolean,false,false,false
-ion-searchbar,prop,autocapitalize,string,undefined,true,false
+ion-searchbar,prop,autocapitalize,string,'default',false,false
 ion-searchbar,prop,autocomplete,"name" | "email" | "tel" | "url" | "on" | "off" | "honorific-prefix" | "given-name" | "additional-name" | "family-name" | "honorific-suffix" | "nickname" | "username" | "new-password" | "current-password" | "one-time-code" | "organization-title" | "organization" | "street-address" | "address-line1" | "address-line2" | "address-line3" | "address-level4" | "address-level3" | "address-level2" | "address-level1" | "country" | "country-name" | "postal-code" | "cc-name" | "cc-given-name" | "cc-additional-name" | "cc-family-name" | "cc-number" | "cc-exp" | "cc-exp-month" | "cc-exp-year" | "cc-csc" | "cc-type" | "transaction-currency" | "transaction-amount" | "language" | "bday" | "bday-day" | "bday-month" | "bday-year" | "sex" | "tel-country-code" | "tel-national" | "tel-area-code" | "tel-local" | "tel-extension" | "impp" | "photo",'off',false,false
 ion-searchbar,prop,autocorrect,"off" | "on",'off',false,false
 ion-searchbar,prop,cancelButtonIcon,string,config.get('backButtonIcon', arrowBackSharp) as string,false,false

core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ionic/core",
-  "version": "7.8.0",
+  "version": "7.8.2",
   "description": "Base components for Ionic",
   "keywords": [
     "ionic",
@@ -43,6 +43,7 @@
     "@capacitor/status-bar": "^5.0.7",
     "@ionic/eslint-config": "^0.3.0",
     "@ionic/prettier-config": "^2.0.0",
+    "@jest/core": "^27.5.1",
     "@playwright/test": "^1.39.0",
     "@rollup/plugin-node-resolve": "^8.4.0",
     "@rollup/plugin-virtual": "^2.0.3",
@@ -50,7 +51,7 @@
     "@stencil/react-output-target": "^0.5.3",
     "@stencil/sass": "^3.0.9",
     "@stencil/vue-output-target": "^0.8.7",
-    "@types/jest": "^29.5.6",
+    "@types/jest": "^27.5.2",
     "@types/node": "^14.6.0",
     "@typescript-eslint/eslint-plugin": "^6.7.2",
     "@typescript-eslint/parser": "^6.7.2",
@@ -60,9 +61,10 @@
     "eslint-config-prettier": "^8.5.0",
     "eslint-plugin-custom-rules": "file:custom-rules",
     "execa": "^5.0.0",
+    "fast-deep-equal": "^3.1.3",
     "fs-extra": "^9.0.1",
-    "jest": "^29.7.0",
-    "jest-cli": "^29.7.0",
+    "jest": "^27.5.1",
+    "jest-cli": "^27.5.1",
     "prettier": "^2.6.1",
     "rollup": "^2.26.4",
     "sass": "^1.33.0",
@@ -71,30 +73,35 @@
     "stylelint-order": "^4.1.0"
   },
   "scripts": {
-    "build": "npm run clean && npm run build.css && stencil build --es5 --docs-json dist/docs.json",
-    "build.css": "npm run css.sass && npm run css.minify",
-    "build.debug": "npm run clean && stencil build --debug",
+    "build": "pnpm run clean && pnpm run build.css && stencil build --es5 --docs-json dist/docs.json",
+    "build.css": "pnpm run css.sass && pnpm run css.minify",
+    "build.debug": "pnpm run clean && stencil build --debug",
     "build.docs.json": "stencil build --docs-json dist/docs.json",
     "clean": "node scripts/clean.js",
     "css.minify": "cleancss -O2 -o ./css/ionic.bundle.css ./css/ionic.bundle.css",
     "css.sass": "sass --embed-sources src/css:./css",
     "eslint": "eslint src",
-    "lint": "npm run lint.ts && npm run lint.sass && npm run prettier -- --write --cache",
-    "lint.fix": "npm run lint.ts.fix && npm run lint.sass.fix && npm run prettier -- --write --cache",
+    "lint": "pnpm run lint.ts && pnpm run lint.sass && pnpm run prettier --write --cache",
+    "lint.fix": "pnpm run lint.ts.fix && pnpm run lint.sass.fix && pnpm run prettier --write --cache",
     "lint.sass": "stylelint \"src/**/*.scss\"",
-    "lint.sass.fix": "npm run lint.sass -- --fix",
-    "lint.ts": "npm run eslint",
-    "lint.ts.fix": "npm run eslint -- --fix",
+    "lint.sass.fix": "pnpm run lint.sass --fix",
+    "lint.ts": "pnpm run eslint",
+    "lint.ts.fix": "pnpm run eslint --fix",
     "prerender.e2e": "node scripts/testing/prerender.js",
     "prettier": "prettier \"./src/**/*.{html,ts,tsx,js,jsx}\"",
-    "start": "npm run build.css && stencil build --dev --watch --serve",
-    "test": "npm run test.spec && npm run test.e2e",
+    "start": "pnpm run build.css && stencil build --dev --watch --serve",
+    "test": "pnpm run test.spec && pnpm run test.e2e",
     "test.spec": "stencil test --spec --max-workers=2",
-    "test.e2e": "npx playwright test",
-    "test.e2e.update-snapshots": "npm run test.e2e -- --update-snapshots",
+    "test.e2e": "pnpm exec playwright test",
+    "test.e2e.update-snapshots": "pnpm run test.e2e --update-snapshots",
     "test.watch": "jest --watch --no-cache",
     "test.treeshake": "node scripts/treeshaking.js dist/index.js",
-    "validate": "npm run lint && npm run test && npm run build && npm run test.treeshake"
+    "validate": "pnpm run lint && pnpm run test && pnpm run build && pnpm run test.treeshake",
+    "docker.build": "docker build -t ionic-playwright .",
+    "test.e2e.docker": "pnpm run docker.build && docker run -it --rm -e DISPLAY=$(cat docker-display.txt) -v $(cat docker-display-volume.txt) --ipc=host --mount=type=bind,source=./,target=/ionic ionic-playwright pnpm run test.e2e --",
+    "test.e2e.docker.update-snapshots": "pnpm run test.e2e.docker -- --update-snapshots",
+    "test.e2e.docker.ci": "pnpm run docker.build && docker run -e CI='true' --rm --ipc=host --mount=type=bind,source=./,target=/ionic ionic-playwright pnpm run test.e2e --",
+    "test.report": "pnpm exec playwright show-report"
   },
   "author": "Ionic Team",
   "license": "MIT",

core/src/components.d.ts

@@ -3211,7 +3211,7 @@ export namespace Components {
     }
     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.
+          * 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';
         /**
@@ -7295,7 +7295,7 @@ declare namespace LocalJSX {
         /**
           * Indicates whether and how the text value should be automatically capitalized as it is entered/edited by the user. Available options: `"off"`, `"none"`, `"on"`, `"sentences"`, `"words"`, `"characters"`.
          */
-        "autocapitalize": string;
+        "autocapitalize"?: string;
         /**
           * Set the input's autocomplete property.
          */
@@ -8037,7 +8037,7 @@ declare namespace LocalJSX {
     }
     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.
+          * 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';
         /**

core/src/components/alert/test/a11y/alert.e2e.ts

@@ -288,6 +288,10 @@ configs({ directions: ['ltr'] }).forEach(({ title, screenshot, config }) => {
       await alert.evaluate((el: HTMLIonAlertElement) => el.present());
       await ionAlertDidPresent.next();
 
+      /**
+       * The borders on the text fields may not be visible in the screenshot
+       * when using Safari, this is due to a WebKit rendering quirk.
+       */
       await expect(page).toHaveScreenshot(screenshot(`alert-text-fields-scale`));
     });
   });

core/src/components/datetime/datetime.tsx

@@ -108,6 +108,7 @@ export class Datetime implements ComponentInterface {
   private calendarBodyRef?: HTMLElement;
   private monthYearToggleItemRef?: HTMLIonItemElement;
   private popoverRef?: HTMLIonPopoverElement;
+  private intersectionTrackerRef?: HTMLElement;
   private clearFocusVisible?: () => void;
   private parsedMinuteValues?: number[];
   private parsedHourValues?: number[];
@@ -1079,6 +1080,8 @@ export class Datetime implements ComponentInterface {
   }
 
   componentDidLoad() {
+    const { el, intersectionTrackerRef } = this;
+
     /**
      * If a scrollable element is hidden using `display: none`,
      * it will not have a scroll height meaning we cannot scroll elements
@@ -1106,7 +1109,7 @@ export class Datetime implements ComponentInterface {
         this.el.classList.add('datetime-ready');
       });
     };
-    const visibleIO = new IntersectionObserver(visibleCallback, { threshold: 0.01 });
+    const visibleIO = new IntersectionObserver(visibleCallback, { threshold: 0.01, root: el });
 
     /**
      * Use raf to avoid a race condition between the component loading and
@@ -1114,7 +1117,7 @@ export class Datetime implements ComponentInterface {
      * could cause the datetime to start at a visibility of 0, erroneously
      * triggering the `hiddenIO` observer below.
      */
-    raf(() => visibleIO?.observe(this.el));
+    raf(() => visibleIO?.observe(intersectionTrackerRef!));
 
     /**
      * We need to clean up listeners when the datetime is hidden
@@ -1144,8 +1147,8 @@ export class Datetime implements ComponentInterface {
         this.el.classList.remove('datetime-ready');
       });
     };
-    const hiddenIO = new IntersectionObserver(hiddenCallback, { threshold: 0 });
-    raf(() => hiddenIO?.observe(this.el));
+    const hiddenIO = new IntersectionObserver(hiddenCallback, { threshold: 0, root: el });
+    raf(() => hiddenIO?.observe(intersectionTrackerRef!));
 
     /**
      * Datetime uses Ionic components that emit
@@ -2613,6 +2616,20 @@ export class Datetime implements ComponentInterface {
           }),
         }}
       >
+        {/*
+          WebKit has a quirk where IntersectionObserver callbacks are delayed until after
+          an accelerated animation finishes if the "root" specified in the config is the
+          browser viewport (the default behavior if "root" is not specified). This means
+          that when presenting a datetime in a modal on iOS the calendar body appears
+          blank until the modal animation finishes.
+
+          We can work around this by observing .intersection-tracker and using the host
+          (ion-datetime) as the "root". This allows the IO callback to fire the moment
+          the datetime is visible. The .intersection-tracker element should not have
+          dimensions or additional styles, and it should not be positioned absolutely
+          otherwise the IO callback may fire at unexpected times.
+        */}
+        <div class="intersection-tracker" ref={(el) => (this.intersectionTrackerRef = el)}></div>
         {this.renderDatetime(mode)}
       </Host>
     );

core/src/components/header/header.ios.scss

@@ -132,8 +132,11 @@
  * We use opacity: 0 to avoid a layout shift.
  * We target both the attribute and the class in the event that the attribute
  * is not reflected on the host in some frameworks.
+ *
+ * Both headers should be scoped to iOS mode otherwise an MD app that uses an
+ * iOS header may cause other MD headers to be unexpectedly hidden.
  */
-ion-header:not(.header-collapse-main):has(~ ion-content ion-header[collapse="condense"], 
-~ ion-content ion-header.header-collapse-condense) {
+ion-header.header-ios:not(.header-collapse-main):has(~ ion-content ion-header.header-ios[collapse="condense"],
+~ ion-content ion-header.header-ios.header-collapse-condense) {
   opacity: 0;
 }

core/src/components/header/test/basic/header.e2e.ts

@@ -85,3 +85,91 @@ configs({ modes: ['ios'], directions: ['ltr'] }).forEach(({ title, screenshot, c
     });
   });
 });
+
+/**
+ * This test only impacts MD applications
+ */
+configs({ modes: ['md'], directions: ['ltr'] }).forEach(({ title, screenshot, config }) => {
+  test.describe(title('header: translucent'), () => {
+    test('should not hide MD headers when using a descendant iOS header in an MD app', async ({ page }) => {
+      test.info().annotations.push({
+        type: 'issue',
+        description: 'https://github.com/ionic-team/ionic-framework/issues/28867',
+      });
+      await page.setContent(
+        `
+        <ion-header id="main-header">
+          <ion-toolbar>
+            <ion-title>Header</ion-title>
+          </ion-toolbar>
+        </ion-header>
+        <ion-content>
+          <ion-header collapse="condense">
+            <ion-toolbar>
+              <ion-title size="large">Header</ion-title>
+            </ion-toolbar>
+          </ion-header>
+
+          <ion-header mode="ios">
+            <ion-toolbar>
+              <ion-title>Welcome</ion-title>
+            </ion-toolbar>
+          </ion-header>
+        </ion-content>
+      `,
+        config
+      );
+
+      const header = page.locator('ion-header#main-header');
+
+      /**
+       * The existence of the iOS header in an MD app should not cause the main MD header
+       * to be hidden. We do not have toHaveVisible because the behavior that hides
+       * the header under correct circumstances does it using opacity: 0.
+       * Playwright considers an element with opacity: 0 to still be visible
+       * because it has a non-zero bounding box.
+       */
+      await expect(header).toHaveScreenshot(screenshot('header-md-visibility-ios-descendant'));
+    });
+    test('should not hide MD headers when using a root iOS header in an MD app', async ({ page }) => {
+      test.info().annotations.push({
+        type: 'issue',
+        description: 'https://github.com/ionic-team/ionic-framework/issues/28867',
+      });
+      await page.setContent(
+        `
+        <ion-header id="main-header" mode="ios">
+          <ion-toolbar>
+            <ion-title>Header</ion-title>
+          </ion-toolbar>
+        </ion-header>
+        <ion-content>
+          <ion-header collapse="condense">
+            <ion-toolbar>
+              <ion-title size="large">Header</ion-title>
+            </ion-toolbar>
+          </ion-header>
+
+          <ion-header>
+            <ion-toolbar>
+              <ion-title>Welcome</ion-title>
+            </ion-toolbar>
+          </ion-header>
+        </ion-content>
+      `,
+        config
+      );
+
+      const header = page.locator('ion-header#main-header');
+
+      /**
+       * The existence of the iOS header in an MD app should not cause the main MD header
+       * to be hidden. We do not have toHaveVisible because the behavior that hides
+       * the header under correct circumstances does it using opacity: 0.
+       * Playwright considers an element with opacity: 0 to still be visible
+       * because it has a non-zero bounding box.
+       */
+      await expect(header).toHaveScreenshot(screenshot('header-md-visibility-ios-main'));
+    });
+  });
+});

core/src/components/item/test/buttons/index.html

@@ -12,165 +12,6 @@
     <script src="../../../../../scripts/testing/scripts.js"></script>
     <script nomodule src="../../../../../dist/ionic/ionic.js"></script>
     <script type="module" src="../../../../../dist/ionic/ionic.esm.js"></script>
-
-    <style>
-      /*
-       * Dark Colors
-       * -------------------------------------------
-       */
-
-      body.dark {
-        --ion-color-primary: #428cff;
-        --ion-color-primary-rgb: 66, 140, 255;
-        --ion-color-primary-contrast: #ffffff;
-        --ion-color-primary-contrast-rgb: 255, 255, 255;
-        --ion-color-primary-shade: #3a7be0;
-        --ion-color-primary-tint: #5598ff;
-
-        --ion-color-secondary: #50c8ff;
-        --ion-color-secondary-rgb: 80, 200, 255;
-        --ion-color-secondary-contrast: #ffffff;
-        --ion-color-secondary-contrast-rgb: 255, 255, 255;
-        --ion-color-secondary-shade: #46b0e0;
-        --ion-color-secondary-tint: #62ceff;
-
-        --ion-color-tertiary: #6a64ff;
-        --ion-color-tertiary-rgb: 106, 100, 255;
-        --ion-color-tertiary-contrast: #ffffff;
-        --ion-color-tertiary-contrast-rgb: 255, 255, 255;
-        --ion-color-tertiary-shade: #5d58e0;
-        --ion-color-tertiary-tint: #7974ff;
-
-        --ion-color-success: #2fdf75;
-        --ion-color-success-rgb: 47, 223, 117;
-        --ion-color-success-contrast: #000000;
-        --ion-color-success-contrast-rgb: 0, 0, 0;
-        --ion-color-success-shade: #29c467;
-        --ion-color-success-tint: #44e283;
-
-        --ion-color-warning: #ffd534;
-        --ion-color-warning-rgb: 255, 213, 52;
-        --ion-color-warning-contrast: #000000;
-        --ion-color-warning-contrast-rgb: 0, 0, 0;
-        --ion-color-warning-shade: #e0bb2e;
-        --ion-color-warning-tint: #ffd948;
-
-        --ion-color-danger: #ff4961;
-        --ion-color-danger-rgb: 255, 73, 97;
-        --ion-color-danger-contrast: #ffffff;
-        --ion-color-danger-contrast-rgb: 255, 255, 255;
-        --ion-color-danger-shade: #e04055;
-        --ion-color-danger-tint: #ff5b71;
-
-        --ion-color-dark: #f4f5f8;
-        --ion-color-dark-rgb: 244, 245, 248;
-        --ion-color-dark-contrast: #000000;
-        --ion-color-dark-contrast-rgb: 0, 0, 0;
-        --ion-color-dark-shade: #d7d8da;
-        --ion-color-dark-tint: #f5f6f9;
-
-        --ion-color-medium: #989aa2;
-        --ion-color-medium-rgb: 152, 154, 162;
-        --ion-color-medium-contrast: #000000;
-        --ion-color-medium-contrast-rgb: 0, 0, 0;
-        --ion-color-medium-shade: #86888f;
-        --ion-color-medium-tint: #a2a4ab;
-
-        --ion-color-light: #222428;
-        --ion-color-light-rgb: 34, 36, 40;
-        --ion-color-light-contrast: #ffffff;
-        --ion-color-light-contrast-rgb: 255, 255, 255;
-        --ion-color-light-shade: #1e2023;
-        --ion-color-light-tint: #383a3e;
-      }
-
-      /*
-       * iOS Dark Theme
-       * -------------------------------------------
-       */
-
-      .ios body.dark {
-        --ion-background-color: #000000;
-        --ion-background-color-rgb: 0, 0, 0;
-
-        --ion-text-color: #ffffff;
-        --ion-text-color-rgb: 255, 255, 255;
-
-        --ion-color-step-50: #0d0d0d;
-        --ion-color-step-100: #1a1a1a;
-        --ion-color-step-150: #262626;
-        --ion-color-step-200: #333333;
-        --ion-color-step-250: #404040;
-        --ion-color-step-300: #4d4d4d;
-        --ion-color-step-350: #595959;
-        --ion-color-step-400: #666666;
-        --ion-color-step-450: #737373;
-        --ion-color-step-500: #808080;
-        --ion-color-step-550: #8c8c8c;
-        --ion-color-step-600: #999999;
-        --ion-color-step-650: #a6a6a6;
-        --ion-color-step-700: #b3b3b3;
-        --ion-color-step-750: #bfbfbf;
-        --ion-color-step-800: #cccccc;
-        --ion-color-step-850: #d9d9d9;
-        --ion-color-step-900: #e6e6e6;
-        --ion-color-step-950: #f2f2f2;
-
-        --ion-item-background: #000000;
-
-        --ion-card-background: #1c1c1d;
-      }
-
-      .ios body.dark ion-modal {
-        --ion-background-color: var(--ion-color-step-100);
-        --ion-toolbar-background: var(--ion-color-step-150);
-        --ion-toolbar-border-color: var(--ion-color-step-250);
-        --ion-item-background: var(--ion-color-step-150);
-      }
-
-      /*
-       * Material Design Dark Theme
-       * -------------------------------------------
-       */
-
-      .md body.dark {
-        --ion-background-color: #121212;
-        --ion-background-color-rgb: 18, 18, 18;
-
-        --ion-text-color: #ffffff;
-        --ion-text-color-rgb: 255, 255, 255;
-
-        --ion-border-color: #222222;
-
-        --ion-color-step-50: #1e1e1e;
-        --ion-color-step-100: #2a2a2a;
-        --ion-color-step-150: #363636;
-        --ion-color-step-200: #414141;
-        --ion-color-step-250: #4d4d4d;
-        --ion-color-step-300: #595959;
-        --ion-color-step-350: #656565;
-        --ion-color-step-400: #717171;
-        --ion-color-step-450: #7d7d7d;
-        --ion-color-step-500: #898989;
-        --ion-color-step-550: #949494;
-        --ion-color-step-600: #a0a0a0;
-        --ion-color-step-650: #acacac;
-        --ion-color-step-700: #b8b8b8;
-        --ion-color-step-750: #c4c4c4;
-        --ion-color-step-800: #d0d0d0;
-        --ion-color-step-850: #dbdbdb;
-        --ion-color-step-900: #e7e7e7;
-        --ion-color-step-950: #f3f3f3;
-
-        --ion-item-background: #1e1e1e;
-
-        --ion-toolbar-background: #1f1f1f;
-
-        --ion-tab-bar-background: #1f1f1f;
-
-        --ion-card-background: #1e1e1e;
-      }
-    </style>
   </head>
 
   <body>
@@ -347,12 +188,6 @@
     </style>
 
     <script>
-      // TODO FW-4005
-      const params = new URL(window.location).searchParams;
-      const dark = params.get('dark');
-      if (dark !== null) {
-        document.body.classList.add('dark');
-      }
       const attach = document.getElementById('attachClick');
 
       attach.addEventListener('click', (ev) => {

core/src/components/item/test/buttons/item.e2e.ts

@@ -19,14 +19,34 @@ configs().forEach(({ title, screenshot, config }) => {
   });
 });
 
-configs({ directions: ['ltr'] }).forEach(({ title, screenshot, config }) => {
+configs({ directions: ['ltr'], themes: ['dark'] }).forEach(({ title, screenshot, config }) => {
   test.describe(title('item: buttons dark'), () => {
     test('should not have visual regressions in dark', async ({ page }) => {
-      await page.goto(`/src/components/item/test/buttons?dark=true`, config);
+      test.info().annotations.push({
+        type: 'issue',
+        description: 'https://github.com/ionic-team/ionic-framework/issues/27130',
+      });
 
-      await page.setIonViewport();
+      await page.setContent(
+        `
+        <ion-list>
+          <ion-item button="true">
+            <ion-label>Button Item</ion-label>
+          </ion-item>
+          <ion-item button="true" class="ion-activated">
+            <ion-label>Activated Button Item</ion-label>
+          </ion-item>
+          <ion-item button="true" class="ion-focused">
+            <ion-label>Focused Button Item</ion-label>
+          </ion-item>
+        </ion-list>
+      `,
+        config
+      );
 
-      await expect(page).toHaveScreenshot(screenshot(`item-buttons-dark-diff`));
+      const list = page.locator('ion-list');
+
+      await expect(list).toHaveScreenshot(screenshot(`item-buttons-dark-diff`));
     });
   });
 });

core/src/components/picker-column-internal/picker-column-internal.tsx

@@ -92,7 +92,11 @@ export class PickerColumnInternal implements ComponentInterface {
    */
   componentWillLoad() {
     const visibleCallback = (entries: IntersectionObserverEntry[]) => {
-      const ev = entries[0];
+      /**
+       * Browsers will sometimes group multiple IO events into a single callback.
+       * As a result, we want to grab the last/most recent event in case there are multiple events.
+       */
+      const ev = entries[entries.length - 1];
 
       if (ev.isIntersecting) {
         const { activeItem, el } = this;