13485 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
ionitron	7bb08f9ce4	chore(): update package lock files	2024-01-31 15:18:19 +00:00
ionitron	e672805406	v7.7.0 v7.7.0	2024-01-31 15:17:39 +00:00
Liam DeBeasi	551065fd9e	chore: sync with main	2024-01-31 10:10:32 -05:00
Liam DeBeasi	775841a397	chore: sync with main	2024-01-31 09:44:05 -05:00
Liam DeBeasi	c998f022ff	merge release-7.6.7 ... Release 7.6.7	2024-01-31 09:43:02 -05:00
ionitron	fae7b24d2a	chore(): update package lock files	2024-01-31 14:27:13 +00:00
ionitron	1de5ff9302	v7.6.7 v7.6.7	2024-01-31 14:26:24 +00:00
Liam DeBeasi	eedafc394b	chore: sync with main ... chore: sync with main	2024-01-31 09:24:08 -05:00
dependabot[bot]	7825eab925	chore(deps-dev): Bump @capacitor/status-bar from 5.0.6 to 5.0.7 in /core (#28931) ... Bumps [@capacitor/status-bar](https://github.com/ionic-team/capacitor-plugins) from 5.0.6 to 5.0.7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/capacitor-plugins/releases"><code>@​capacitor/status-bar</code>'s releases</a>.</em></p> <blockquote> <h2><code>@​capacitor/status-bar</code><a href="https://github.com/5"><code>@​5</code></a>.0.7</h2> <h2><a href="https://github.com/ionic-team/capacitor-plugins/compare/@capacitor/status-bar@5.0.6...@capacitor/status-bar@5.0.7">5.0.7</a> (2024-01-29)</h2> <p><strong>Note:</strong> Version bump only for package <code>@​capacitor/status-bar</code></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="d5483ce9f6"><code>d5483ce</code></a> chore(release): publish [skip ci]</li> <li><a href="be9ff28e06"><code>be9ff28</code></a> docs: fix addListener links (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/2012">#2012</a>)</li> <li><a href="d8540feeb6"><code>d8540fe</code></a> fix(screen-orientation) Add ScreenOrientationLockType (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/2005">#2005</a>)</li> <li><a href="e2cdf3538b"><code>e2cdf35</code></a> feat(browser): implement close() method for android</li> <li><a href="f9afbe9b03"><code>f9afbe9</code></a> fix(filesystem): requestPermissions not resolving (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/1991">#1991</a>)</li> <li><a href="c5aab483fe"><code>c5aab48</code></a> chore(release): publish [skip ci]</li> <li><a href="77dc373b41"><code>77dc373</code></a> fix(camera): reject promise on web input cancel event (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/1964">#1964</a>)</li> <li><a href="bf7ec3306e"><code>bf7ec33</code></a> feat(google-maps): Separate mapId for Google Maps Cloud IDs (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/1943">#1943</a>)</li> <li><a href="3b520b8455"><code>3b520b8</code></a> fix(keyboard): Change keyboard style during setStyle (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/1935">#1935</a>)</li> <li><a href="e18f458533"><code>e18f458</code></a> docs(screen-reader): Use stateChange event in example code (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/1934">#1934</a>)</li> <li>Additional commits viewable in <a href="https://github.com/ionic-team/capacitor-plugins/compare/@capacitor/status-bar@5.0.6...@capacitor/status-bar@5.0.7">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-31 01:59:39 +00:00
Liam DeBeasi	219e630ed5	chore: sync with main	2024-01-30 20:08:55 -05:00
Liam DeBeasi	bf34e0e247	test: migrate form control usages to modern syntax (#28897) ... Issue number: Internal --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> Several tests were still using the legacy form syntax. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Migrated tests in `core`, `angular`, and `vue` to use the modern form syntax (`react` did not have form controls). I opted not to migrate `item/test/highlight` and `item/test/counter` because those tests are going to be removed in the future once the deprecate item APIs are removed. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> --------- Co-authored-by: ionitron <hi@ionicframework.com> Co-authored-by: Maria Hutt <thetaPC@users.noreply.github.com>	2024-01-30 16:14:02 +00:00
Yumi Izumi	f6fc22bba6	fix(action-sheet, alert, toast): button roles autocomplete with available options (#27940) ... Issue number: resolves #27965 --------- https://www.youtube.com/watch?v=a_m7jxrTlaw&list=PLIvujZeVDLMx040-j1W4WFs1BxuTGdI_b&index=3 <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> There is a lack of autocomplete support for AlertButton attribute of `role` (there may be similar situations for other components too, however, I was working on this component and found it). ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Support for autocomplete for the two types defined `cancel` and `destructive`, and also supports any arbitrary string if passed in. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> I suggest there to be some global interface similar to the following: ``` interface LooseAutocomplete<T extends string> = T | Omit<string, T>; ``` I referenced this great [video](https://youtu.be/a_m7jxrTlaw) from Matt @mattpocock --------- Co-authored-by: Liam DeBeasi <liamdebeasi@users.noreply.github.com>	2024-01-30 14:53:40 +00:00
dependabot[bot]	e021eadb81	chore(deps-dev): Bump @capacitor/keyboard from 5.0.7 to 5.0.8 in /core (#28913) ... Bumps [@capacitor/keyboard](https://github.com/ionic-team/capacitor-plugins) from 5.0.7 to 5.0.8. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/capacitor-plugins/releases"><code>@​capacitor/keyboard</code>'s releases</a>.</em></p> <blockquote> <h2><code>@​capacitor/keyboard</code><a href="https://github.com/5"><code>@​5</code></a>.0.8</h2> <h2><a href="https://github.com/ionic-team/capacitor-plugins/compare/@capacitor/keyboard@5.0.7...@capacitor/keyboard@5.0.8">5.0.8</a> (2024-01-29)</h2> <p><strong>Note:</strong> Version bump only for package <code>@​capacitor/keyboard</code></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="d5483ce9f6"><code>d5483ce</code></a> chore(release): publish [skip ci]</li> <li><a href="be9ff28e06"><code>be9ff28</code></a> docs: fix addListener links (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/2012">#2012</a>)</li> <li><a href="d8540feeb6"><code>d8540fe</code></a> fix(screen-orientation) Add ScreenOrientationLockType (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/2005">#2005</a>)</li> <li><a href="e2cdf3538b"><code>e2cdf35</code></a> feat(browser): implement close() method for android</li> <li><a href="f9afbe9b03"><code>f9afbe9</code></a> fix(filesystem): requestPermissions not resolving (<a href="https://redirect.github.com/ionic-team/capacitor-plugins/issues/1991">#1991</a>)</li> <li>See full diff in <a href="https://github.com/ionic-team/capacitor-plugins/compare/@capacitor/keyboard@5.0.7...@capacitor/keyboard@5.0.8">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-30 02:57:04 +00:00
dependabot[bot]	a1e7694490	chore(deps): Bump @stencil/core from 4.11.0 to 4.12.0 in /core (#28914) ... Bumps [@stencil/core](https://github.com/ionic-team/stencil) from 4.11.0 to 4.12.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/stencil/releases"><code>@​stencil/core</code>'s releases</a>.</em></p> <blockquote> <h2>🌅 4.12.0 (2024-01-29)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>hmr:</strong> allow changes to component decorators when using HMR (<a href="https://redirect.github.com/ionic-team/stencil/issues/5290">#5290</a>) (<a href="656355fc75">656355f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>runtime:</strong> automatically insert <code>key</code> attrs during compilation (<a href="https://redirect.github.com/ionic-team/stencil/issues/5143">#5143</a>) (<a href="9c47438a9a">9c47438</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/stencil/blob/main/CHANGELOG.md"><code>@​stencil/core</code>'s changelog</a>.</em></p> <blockquote> <h1>🌅 <a href="https://github.com/ionic-team/stencil/compare/v4.11.0...v4.12.0">4.12.0</a> (2024-01-29)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>hmr:</strong> allow changes to component decorators when using HMR (<a href="https://redirect.github.com/ionic-team/stencil/issues/5290">#5290</a>) (<a href="656355fc75">656355f</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>runtime:</strong> automatically insert <code>key</code> attrs during compilation (<a href="https://redirect.github.com/ionic-team/stencil/issues/5143">#5143</a>) (<a href="9c47438a9a">9c47438</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="89816e1032"><code>89816e1</code></a> v4.12.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5302">#5302</a>)</li> <li><a href="ccaa7fd7cc"><code>ccaa7fd</code></a> chore(deps): update dependency <code>@​types/node</code> to v20.11.6 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5297">#5297</a>)</li> <li><a href="200d40ac5e"><code>200d40a</code></a> chore(deps): update dependency dts-bundle-generator to v9.2.5 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5298">#5298</a>)</li> <li><a href="106dc0e2b6"><code>106dc0e</code></a> chore(deps): update dependency esbuild to v0.19.12 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5299">#5299</a>)</li> <li><a href="9c47438a9a"><code>9c47438</code></a> feat(runtime): automatically insert <code>key</code> attrs during compilation (<a href="https://redirect.github.com/ionic-team/stencil/issues/5143">#5143</a>)</li> <li><a href="278c336166"><code>278c336</code></a> chore(config): add some documentation to the <code>buildDist</code> option (<a href="https://redirect.github.com/ionic-team/stencil/issues/5296">#5296</a>)</li> <li><a href="e6d97fec9b"><code>e6d97fe</code></a> chore(repo): add docs section to pr template (<a href="https://redirect.github.com/ionic-team/stencil/issues/5293">#5293</a>)</li> <li><a href="bdedd8289e"><code>bdedd82</code></a> chore(snc): resolve strictNullChecks for typescript-config (<a href="https://redirect.github.com/ionic-team/stencil/issues/5294">#5294</a>)</li> <li><a href="5ac2f5defd"><code>5ac2f5d</code></a> chore(docs): add a step for creating a new version of the stencil docs (<a href="https://redirect.github.com/ionic-team/stencil/issues/5295">#5295</a>)</li> <li><a href="5f3e04f3d9"><code>5f3e04f</code></a> chore(readme): remove broken image (<a href="https://redirect.github.com/ionic-team/stencil/issues/5291">#5291</a>)</li> <li>Additional commits viewable in <a href="https://github.com/ionic-team/stencil/compare/v4.11.0...v4.12.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-30 02:55:51 +00:00
dependabot[bot]	07b987d034	chore(deps-dev): Bump @stencil/sass from 3.0.8 to 3.0.9 in /core (#28912) ... Bumps [@stencil/sass](https://github.com/ionic-team/stencil-sass) from 3.0.8 to 3.0.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/stencil-sass/releases"><code>@​stencil/sass</code>'s releases</a>.</em></p> <blockquote> <h2>v3.0.9</h2> <h2>What's Changed</h2> <h3>Bug Fixes</h3> <ul> <li>fix(plugin): normalize dependency path by <a href="https://github.com/christian-bromann"><code>@​christian-bromann</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/459">ionic-team/stencil-sass#459</a></li> </ul> <h3>Dependency Updates</h3> <ul> <li>chore(deps): update dependency np to v9.2.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/451">ionic-team/stencil-sass#451</a></li> <li>chore(deps): update actions/setup-node action to v4.0.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/454">ionic-team/stencil-sass#454</a></li> <li>chore(deps): update dependency <code>@​stencil/core</code> to v4.9.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/455">ionic-team/stencil-sass#455</a></li> <li>chore(deps): update dependency prettier to v3.1.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/452">ionic-team/stencil-sass#452</a></li> <li>chore(deps): update dependency <code>@​stencil/core</code> to v4.9.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/456">ionic-team/stencil-sass#456</a></li> <li>chore(deps): update dependency npm to v10.3.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/457">ionic-team/stencil-sass#457</a></li> <li>chore(deps): update dependency prettier to v3.2.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/458">ionic-team/stencil-sass#458</a></li> <li>chore(deps): update node.js to v20.11.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/443">ionic-team/stencil-sass#443</a></li> <li>chore(deps): update dependency rollup to v4.9.5 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/442">ionic-team/stencil-sass#442</a></li> <li>chore(deps): update dependency prettier to v3.2.2 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/460">ionic-team/stencil-sass#460</a></li> <li>chore(deps): update dependency <code>@​stencil/core</code> to v4.10.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/462">ionic-team/stencil-sass#462</a></li> <li>chore(deps): update dependency terser to v5.27.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/464">ionic-team/stencil-sass#464</a></li> <li>chore(deps): update dependency prettier to v3.2.4 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/463">ionic-team/stencil-sass#463</a></li> <li>chore(build): improve build process by <a href="https://github.com/christian-bromann"><code>@​christian-bromann</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/461">ionic-team/stencil-sass#461</a></li> <li>chore(deps): update dependency rollup to v4.9.6 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/465">ionic-team/stencil-sass#465</a></li> <li>chore(deps): update dependency <code>@​stencil/core</code> to v4.11.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/466">ionic-team/stencil-sass#466</a></li> <li>chore(deps): update dependency npm to v10.4.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/468">ionic-team/stencil-sass#468</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/christian-bromann"><code>@​christian-bromann</code></a> made their first contribution in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/459">ionic-team/stencil-sass#459</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/ionic-team/stencil-sass/compare/v3.0.8...v3.0.9">https://github.com/ionic-team/stencil-sass/compare/v3.0.8...v3.0.9</a></p> <h2>v3.0.9-0</h2> <h2>What's Changed</h2> <ul> <li>chore(deps): update dependency np to v9.2.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/451">ionic-team/stencil-sass#451</a></li> <li>chore(deps): update actions/setup-node action to v4.0.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/454">ionic-team/stencil-sass#454</a></li> <li>chore(deps): update dependency <code>@​stencil/core</code> to v4.9.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/455">ionic-team/stencil-sass#455</a></li> <li>chore(deps): update dependency prettier to v3.1.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/452">ionic-team/stencil-sass#452</a></li> <li>chore(deps): update dependency <code>@​stencil/core</code> to v4.9.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/456">ionic-team/stencil-sass#456</a></li> <li>chore(deps): update dependency npm to v10.3.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/457">ionic-team/stencil-sass#457</a></li> <li>chore(deps): update dependency prettier to v3.2.1 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/458">ionic-team/stencil-sass#458</a></li> <li>chore(deps): update node.js to v20.11.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/443">ionic-team/stencil-sass#443</a></li> <li>chore(deps): update dependency rollup to v4.9.5 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/442">ionic-team/stencil-sass#442</a></li> <li>chore(deps): update dependency prettier to v3.2.2 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/460">ionic-team/stencil-sass#460</a></li> <li>chore(deps): update dependency <code>@​stencil/core</code> to v4.10.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/462">ionic-team/stencil-sass#462</a></li> <li>fix(plugin): normalize dependency path by <a href="https://github.com/christian-bromann"><code>@​christian-bromann</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/459">ionic-team/stencil-sass#459</a></li> <li>chore(deps): update dependency terser to v5.27.0 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/464">ionic-team/stencil-sass#464</a></li> <li>chore(deps): update dependency prettier to v3.2.4 by <a href="https://github.com/renovate"><code>@​renovate</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/463">ionic-team/stencil-sass#463</a></li> <li>chore(build): improve build process by <a href="https://github.com/christian-bromann"><code>@​christian-bromann</code></a> in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/461">ionic-team/stencil-sass#461</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/christian-bromann"><code>@​christian-bromann</code></a> made their first contribution in <a href="https://redirect.github.com/ionic-team/stencil-sass/pull/459">ionic-team/stencil-sass#459</a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="75b8253755"><code>75b8253</code></a> 3.0.9</li> <li><a href="b2ac91a7db"><code>b2ac91a</code></a> chore(deps): update dependency npm to v10.4.0 (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/468">#468</a>)</li> <li><a href="946e7322e5"><code>946e732</code></a> chore(deps): update dependency <code>@​stencil/core</code> to v4.11.0 (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/466">#466</a>)</li> <li><a href="9da4825c7d"><code>9da4825</code></a> chore(deps): update dependency rollup to v4.9.6 (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/465">#465</a>)</li> <li><a href="ca0d500ec6"><code>ca0d500</code></a> 3.0.9-0</li> <li><a href="21e7a77ad2"><code>21e7a77</code></a> chore(build): improve build process (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/461">#461</a>)</li> <li><a href="6774845feb"><code>6774845</code></a> chore(deps): update dependency prettier to v3.2.4 (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/463">#463</a>)</li> <li><a href="555401c8d7"><code>555401c</code></a> chore(deps): update dependency terser to v5.27.0 (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/464">#464</a>)</li> <li><a href="3ef9e400c2"><code>3ef9e40</code></a> fix(plugin): normalize dependency path (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/459">#459</a>)</li> <li><a href="fa5740376d"><code>fa57403</code></a> chore(deps): update dependency <code>@​stencil/core</code> to v4.10.0 (<a href="https://redirect.github.com/ionic-team/stencil-sass/issues/462">#462</a>)</li> <li>Additional commits viewable in <a href="https://github.com/ionic-team/stencil-sass/compare/v3.0.8...v3.0.9">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-29 23:21:01 +00:00
dependabot[bot]	58639c7a1e	chore(deps): Bump @stencil/core from 4.10.0 to 4.11.0 in /core (#28866) ... Bumps [@stencil/core](https://github.com/ionic-team/stencil) from 4.10.0 to 4.11.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/stencil/releases"><code>@​stencil/core</code>'s releases</a>.</em></p> <blockquote> <h2>🍝 4.11.0 (2024-01-22)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>runtime:</strong> resolve memory leak caused by global content ref (<a href="https://redirect.github.com/ionic-team/stencil/issues/5266">#5266</a>) (<a href="fb1b3f5a5b">fb1b3f5</a>)</li> <li><strong>screenshot:</strong> recognise clip options (<a href="https://redirect.github.com/ionic-team/stencil/issues/5205">#5205</a>) (<a href="0d61a53a24">0d61a53</a>)</li> <li><strong>style:</strong> fixes to watching nested and multiple styles on Stencil components (<a href="https://redirect.github.com/ionic-team/stencil/issues/5244">#5244</a>) (<a href="fa5ab1b75f">fa5ab1b</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>compiler:</strong> deprecate customResolveOptions config option (<a href="https://redirect.github.com/ionic-team/stencil/issues/5269">#5269</a>) (<a href="6faf746990">6faf746</a>)</li> <li><strong>deps:</strong> upgrade rollup, commonjs plugin (<a href="https://redirect.github.com/ionic-team/stencil/issues/5274">#5274</a>) (<a href="661120c652">661120c</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/stencil/blob/main/CHANGELOG.md"><code>@​stencil/core</code>'s changelog</a>.</em></p> <blockquote> <h1>🍝 <a href="https://github.com/ionic-team/stencil/compare/v4.10.0...v4.11.0">4.11.0</a> (2024-01-22)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>runtime:</strong> resolve memory leak caused by global content ref (<a href="https://redirect.github.com/ionic-team/stencil/issues/5266">#5266</a>) (<a href="fb1b3f5a5b">fb1b3f5</a>)</li> <li><strong>screenshot:</strong> recognise clip options (<a href="https://redirect.github.com/ionic-team/stencil/issues/5205">#5205</a>) (<a href="0d61a53a24">0d61a53</a>)</li> <li><strong>style:</strong> fixes to watching nested and multiple styles on Stencil components (<a href="https://redirect.github.com/ionic-team/stencil/issues/5244">#5244</a>) (<a href="fa5ab1b75f">fa5ab1b</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>compiler:</strong> deprecate customResolveOptions config option (<a href="https://redirect.github.com/ionic-team/stencil/issues/5269">#5269</a>) (<a href="6faf746990">6faf746</a>)</li> <li><strong>deps:</strong> upgrade rollup, commonjs plugin (<a href="https://redirect.github.com/ionic-team/stencil/issues/5274">#5274</a>) (<a href="661120c652">661120c</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="b2ec143e8c"><code>b2ec143</code></a> Release v4.11.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5285">#5285</a>)</li> <li><a href="36443725e8"><code>3644372</code></a> chore(deps): update typescript-eslint to v6.19.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5283">#5283</a>)</li> <li><a href="1a75ab0991"><code>1a75ab0</code></a> chore(deps): update actions/upload-artifact action to v4.2.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5281">#5281</a>)</li> <li><a href="9c8ed64b06"><code>9c8ed64</code></a> chore(deps): update dependency autoprefixer to v10.4.17 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5279">#5279</a>)</li> <li><a href="e1fc49f9bf"><code>e1fc49f</code></a> chore(deps): update dependency terser to v5.27.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5282">#5282</a>)</li> <li><a href="ff8c4e55d3"><code>ff8c4e5</code></a> chore(deps): update dependency prettier to v3.2.4 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5280">#5280</a>)</li> <li><a href="fa5ab1b75f"><code>fa5ab1b</code></a> fix(style): fixes to watching nested and multiple styles on Stencil component...</li> <li><a href="661120c652"><code>661120c</code></a> feat(deps): upgrade rollup, commonjs plugin (<a href="https://redirect.github.com/ionic-team/stencil/issues/5274">#5274</a>)</li> <li><a href="6faf746990"><code>6faf746</code></a> feat(compiler): deprecate customResolveOptions config option (<a href="https://redirect.github.com/ionic-team/stencil/issues/5269">#5269</a>)</li> <li><a href="493250f150"><code>493250f</code></a> chore(compiler): resolve strictNullCheck for element-decorator (<a href="https://redirect.github.com/ionic-team/stencil/issues/5264">#5264</a>)</li> <li>Additional commits viewable in <a href="https://github.com/ionic-team/stencil/compare/v4.10.0...v4.11.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-29 21:47:44 +00:00
Liam DeBeasi	b1c4c72474	refactor(react, react-router): build works on windows (#28904) ... Issue number: Internal --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> React and React Router packages do not build correctly on Windows because certain dependencies were not marked as external. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - 3rd party packages are correctly marked as external ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->	2024-01-29 18:15:50 +00:00
Liam DeBeasi	9448783bb1	fix(item): only default slot content wraps (#28773) ... Issue number: resolves #28769 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> As part of https://github.com/ionic-team/ionic-framework/pull/28146, we allowed text wrapping inside of `ion-item` for accessibility purposes. One of the behaviors we added was to allow start, default, and end slotted containers to wrap to the next line to align with the iOS spec. However, this decision was based on an incorrect assumption. The following screenshot shows the Settings app on iOS: | default scale | 310% scale | | - | - | | <img width="1170" alt="Frame 4" src="https://github.com/ionic-team/ionic-framework/assets/2721089/462ef153-a060-41c8-9a00-f0aad17839be"> | <img width="1170" alt="Frame 5" src="https://github.com/ionic-team/ionic-framework/assets/2721089/f047f880-7b80-4710-939b-96da075fbbf9"> | At the default scale, the blue icon is in the iOS equivalent of the "start" slot, "Bluetooth" is in the default slot, and "On" is in the "end" slot. We incorrectly assumed the same markup was true when scaling the text up. However, at 310% scale the icon, "Bluetooth" text, and "On" text all become part of the default slot in a single container that wraps. You can tell because the bottom border runs underneath the blue icon at 310% whereas it does not at the default scale. This allows the text to wrap underneath the blue icon. When we originally implemented #28146 we thought that this meant the start, default, and end slot containers should wrap to the next line. I further validated this behavior by creating an app with Swift UI. I created a list of items where each item has the native equivalent of a checkbox in the `start` slot and multiple `ion-labels` in the default slot of the item: | Default Scale | 310% Scale | | - | - | |  |  | The content within each label wraps within the container, but the containers themselves never wrap to the next line. Demo code: ```swift import SwiftUI struct ContentView: View { struct Item: Identifiable, Hashable { let id = UUID() } private var items = [ Item(), Item(), Item(), Item(), Item() ] @State private var multiSelection = Set<UUID>() var body: some View { NavigationView { List(items, selection: $multiSelection) {_ in HStack { Text("Column 1 with really long text") Text("Column 2 with really long text") Text("Column 3 with really long text") Text("Column 4 with really long text") } } .toolbar { EditButton() } } Text("\(multiSelection.count) selections") } } #Preview { ContentView() } ``` ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - This PR removes the ability for the start, default, and end slot containers to wrap to the next line. This behavior aligns with pre-v7.6.0 behaviors. The containers inside of the default slot will not wrap to the next line. However, content within each container (such as text within an `ion-label`) will continue to wrap to meet the team's accessibility requirements. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Dev build: `7.6.5-dev.11704916749.1e64a3a7` --------- Co-authored-by: ionitron <hi@ionicframework.com>	2024-01-26 22:14:48 +00:00
Amanda Johnston	720a3cea99	test(react): re-enable picker tests (#28885) ... Issue number: N/A --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> The `IonPicker` tests in the React app were skipped due to a Stencil bug that has since been resolved. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> Tests re-enabled. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->	2024-01-26 21:16:14 +00:00
dependabot[bot]	b81d85a401	chore(deps-dev): Bump @axe-core/playwright from 4.8.3 to 4.8.4 in /core (#28887) ... Bumps [@axe-core/playwright](https://github.com/dequelabs/axe-core-npm) from 4.8.3 to 4.8.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/dequelabs/axe-core-npm/releases"><code>@​axe-core/playwright</code>'s releases</a>.</em></p> <blockquote> <h2>Release 4.8.4</h2> <h2>What's Changed</h2> <ul> <li>chore: RC v4.8.3 by <a href="https://github.com/github-actions"><code>@​github-actions</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/983">dequelabs/axe-core-npm#983</a></li> <li>chore: bump puppeteer from 19.7.3 to 21.7.0 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/979">dequelabs/axe-core-npm#979</a></li> <li>Release v4.8.3 by <a href="https://github.com/dequejenn"><code>@​dequejenn</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/986">dequelabs/axe-core-npm#986</a></li> <li>chore: bump the npm-low-risk group with 11 updates by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/982">dequelabs/axe-core-npm#982</a></li> <li>chore: bump follow-redirects from 1.15.2 to 1.15.5 by <a href="https://github.com/dependabot"><code>@​dependabot</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/988">dequelabs/axe-core-npm#988</a></li> <li>chore: merge master into develop by <a href="https://github.com/github-actions"><code>@​github-actions</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/987">dequelabs/axe-core-npm#987</a></li> <li>ci: add env var required for creating gh releases by <a href="https://github.com/michael-siek"><code>@​michael-siek</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/989">dequelabs/axe-core-npm#989</a></li> <li>ci: remove deprecated release candidate action by <a href="https://github.com/michael-siek"><code>@​michael-siek</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/990">dequelabs/axe-core-npm#990</a></li> <li>fix(webdriverjs): use new headless argument to fix selenium-webdriver@4.17.0 breaking release by <a href="https://github.com/straker"><code>@​straker</code></a> in <a href="https://redirect.github.com/dequelabs/axe-core-npm/pull/992">dequelabs/axe-core-npm#992</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/dequelabs/axe-core-npm/compare/v4.8.3...4.8.4">https://github.com/dequelabs/axe-core-npm/compare/v4.8.3...4.8.4</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/dequelabs/axe-core-npm/blob/develop/CHANGELOG.md"><code>@​axe-core/playwright</code>'s changelog</a>.</em></p> <blockquote> <h1>Change Log</h1> <p>All notable changes to this project will be documented in this file. See <a href="https://conventionalcommits.org">Conventional Commits</a> for commit guidelines.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="0daba98684"><code>0daba98</code></a> fix(webdriverjs): use new headless argument to fix selenium-webdriver@4.17.0 ...</li> <li><a href="2220400acd"><code>2220400</code></a> ci: remove deprecated release candidate action (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/990">#990</a>)</li> <li><a href="4f295d393a"><code>4f295d3</code></a> ci: add env var required for creating gh releases (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/989">#989</a>)</li> <li><a href="81aefd5646"><code>81aefd5</code></a> Merge pull request <a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/987">#987</a> from dequelabs/master</li> <li><a href="7d49d53bbb"><code>7d49d53</code></a> Merge branch 'develop' into master</li> <li><a href="92669c1ea1"><code>92669c1</code></a> chore: bump follow-redirects from 1.15.2 to 1.15.5 (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/988">#988</a>)</li> <li><a href="dc380aa885"><code>dc380aa</code></a> chore: bump the npm-low-risk group with 11 updates (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/982">#982</a>)</li> <li><a href="3ceecac297"><code>3ceecac</code></a> Merge pull request <a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/986">#986</a> from dequelabs/release</li> <li><a href="6b60442cbd"><code>6b60442</code></a> chore: bump puppeteer from 19.7.3 to 21.7.0 (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/979">#979</a>)</li> <li><a href="54b75d095a"><code>54b75d0</code></a> Merge pull request <a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/983">#983</a> from dequelabs/release-2024-01-09</li> <li>See full diff in <a href="https://github.com/dequelabs/axe-core-npm/compare/v4.8.3...4.8.4">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-26 21:16:03 +00:00
Maria Hutt	aecbc92e30	refactor(ga-screenshots): option to test single component (#27841) ... Issue number: N/A --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> All the E2E tests are run when performing the "Update Reference Screenshots" GitHub actions.  ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - All E2E tests still run as default. - The GH action has the option to run a specific component instead of all tests. - A specified component has the option to run all tests that include the component's name in the file path - A specified component has the option to run all tests that are in the component's folder - If a single component is selected, then the default is to only run tests inside it's folder.  ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> How to test: 1. Create a new branch based off this one 2. Make a style change 3. Push it to the new branch 4. Update the reference images using the new branch 5. This will show you all the options Recommended to test: - a component with the ion prefix (`ion-button`) - a component without the prefix (`button`) - a component that doesn't exist (`random-component`) - no provided component, leave the first input blank - the checkbox --------- Co-authored-by: Liam DeBeasi <liamdebeasi@users.noreply.github.com>	2024-01-26 19:26:22 +00:00
Bernardo Cardoso	bf7922c8b3	fix(item): ensure button focus state on property change (#28892) ... Issue number: resolves #28525 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> When navigated via tab-key, the ion-item is not highlighted correctly after switching from button=false to button=true. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> Now, when dynamically changing the the `button` option to `True`, there's a `@watch` callback that will make sure the internal `isFocusable` `@state` will be updated. - A new unit test was added to item/test. As there was still any unit test for the `ion-item`, a new files was created - `item.spec.tsx` ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> New behavior in runtime:  --------- Co-authored-by: Sean Perkins <sean@ionic.io>	2024-01-26 17:08:47 +00:00
Maria Hutt	2a3c26e44d	test(many): replace waitForSelector with waitFor (#28888) ... Issue number: N/A --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> There are some tests that use Playwright's `waitForSelector` [function](https://playwright.dev/docs/api/class-page#page-wait-for-selector). However, Playwright has informed the community to not use this function by labeling it as [discouraged](https://playwright.dev/docs/api/class-page#page-wait-for-selector). ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Replaced `waitForSelector` with the [recommended](https://playwright.dev/docs/api/class-page#page-wait-for-selector) `waitFor` [function](https://playwright.dev/docs/api/class-locator#locator-wait-for). ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> N/A	2024-01-26 16:32:40 +00:00
Liam DeBeasi	ddd8b92235	chore: remove old link scripts (#28886) ... This script was used to aid in the test of local version of `@ionic/angular`. However, these instructions have been replaced by the instructions in `packages/angular/test/README.md`. This PR removes the old script.	2024-01-25 20:15:28 +00:00
Liam DeBeasi	9a092c03cc	chore: assign team members instead of members from team (#28880) ... The token I was using didn't have the correct permissions, and I need to figure out how to generate a new token (I don't think I have access to the account where these tokens live). For now, I'm going to hard code the team members until I can figure out the token access out.	2024-01-25 15:53:10 +00:00
Liam DeBeasi	a3ebca0f26	chore(ci): auto assign issues (#28873) ... To make it easy for the team to quickly triage issues, we'd like to automatically assign issues to team members at random. This PR use https://github.com/marketplace/actions/auto-assign-issue to assign 1 member of the `framework` GitHub team to be the person to triage.	2024-01-24 22:49:16 +00:00
Shawn Taylor	e10f49c43d	fix(accordion): prevent opening of readonly accordion using keyboard (#28865) ... Issue number: resolves #28344 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> When an Accordion is inside an Accordion Group, and the Accordion Group is enabled and not readonly but the Accordion is disabled and/or readonly, it is possible to navigate to the accordion and open it using the keyboard. This should not be allowed, just like opening it on click is not allowed. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - A disabled Accordion inside an Accordion Group may not be opened via the keyboard. - A readonly Accordion inside an Accordion Group may not be opened via the keyboard. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->	2024-01-24 19:57:36 +00:00
Liam DeBeasi	e41a1a127b	merge release-7.6.6 ... Release 7.6.6	2024-01-24 09:48:22 -05:00
ionitron	67bee73513	chore(): update package lock files	2024-01-24 14:15:49 +00:00
ionitron	0c4e1fcdb4	v7.6.6 v7.6.6	2024-01-24 14:15:07 +00:00
Liam DeBeasi	9603a4de36	fix(menu): improve reliability of main content not being scrollable when menu opens (#28829) ... Issue number: resolves #28399 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> As part of https://github.com/ionic-team/ionic-framework/pull/26976 I fixed an issue where `pointer-events: none` was not applied until after the menu open gesture finishes. This resolved a bug where scrolling was latching after the menu gesture starts. However, I did not account for the edge case where scrolling latches _before_ `pointer-events: none` is applied in the DOM. Since scrolling has already latched then `pointer-events: none` does not change the scrolling behavior. This can happen if a user swipes up and to the right from the left edge of the screen. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - `overflow-y: hidden` is now applied to the scrollable content which will interrupt any scrolling when the menu is open. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Testing: This bug fixes a timing issue where scrolling latches on the main content as the menu tries to open. As a result, I am unable to write reliable automated tests for this. Reviewers should perform the following test on iOS and Android physical devices: 1. Open `src/components/menu/test/basic`. 2. Add enough elements to the main page content such that it scrolls (I added a list with items). 3. On each device, attempt to scroll the main content while also opening the menu on the starting edge of the screen. Scrolling on the main content should not happen if the menu opens. Dev build: `7.6.5-dev.11705341148.1a550d3b`	2024-01-23 19:24:56 +00:00
Liam DeBeasi	10c38d0354	fix(popover): content inside of popover scrolls correctly (#28861) ... Issue number: resolves #28455 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> The main `ion-content` inside of a popover is not scrollable. Instead, the `.popover-viewport` container is scrolled because certain styles no longer applied once we moved popover to the Shadow DOM. This bug impacted the linked issue because it meant that the infinite scroll inside of the content never fires (since the content never scrolls). ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - The `.popover-viewport` rule now targets slotted content with the`.popover-viewport` class. This class is added to the root node that is slotted. This enables us to target the user's content in the light dom. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Dev build: `7.6.6-dev.11705696534.177666f8` --------- Co-authored-by: ionitron <hi@ionicframework.com>	2024-01-23 14:30:14 +00:00
Liam DeBeasi	e86f4f1cc9	chore(ci): do not publish GitHub releases for nightlies (#28853) ... Publishing GitHub releases for each nightly is creating more noise than the team would like. As a result, we are going to stop publishing the GitHub release. However, nightly builds will continue to automatically release. Developers can look at the commits in `main` to determine if a commit is in a nightly build: https://github.com/ionic-team/ionic-framework	2024-01-22 15:15:24 +00:00
Liam DeBeasi	5bc439961f	fix(vue): tabs and parameterized routes work with latest vue (#28846) ... Issue number: resolves #28774 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> There are two issues causing Ionic Vue apps to not behave as intended with certain versions of Vue: 1. In Vue 3.3 a [breaking change shipped](https://github.com/vuejs/core/issues/9916) that changes the default behavior of the `watch` inside of IonRouterOutlet to be a shallow watcher instead of a deep watcher. This caused the router outlet to not consistent re-render. While the change was later reverted by the Vue team, they expressed that the change [may re-land in a future minor release](https://github.com/vuejs/core/issues/9965#issuecomment-1875067499). As a result, we will need to account for this inside of Ionic. 2. In Vue 3.2 a [custom elements improvement shipped](https://github.com/vuejs/core/blob/main/changelogs/CHANGELOG-3.2.md#3238-2022-08-30) that changed how custom elements are referred to in VNodes. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - The affected `watch` call now is now explicitly a deep watcher. This change is backwards compatible as well as forward compatible with upcoming Vue changes. - Updated IonTabs to account for the new VNode behavior for custom elements. Ionic still supports version of Vue that do not have this improvement, so we need to account for both behaviors for now. I also added a tech debt ticket to remove the old checks when we drop support for older versions of Vue. - Updated E2E test dependencies. During this update some of our tests needed to be updated to account for newer versions of Vue/Vitest. Overall I was able to simplify a lot of our tests as a result. I plan to add renovatebot to these E2E test apps, but I will handle that in a separate PR. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 4. Update the BREAKING.md file with the breaking change. 5. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Dev build: `7.6.6-dev.11705526292.1bc0acb5` Note: Both of the issues cause tests to fail when using the latest dependencies in the Vue E2E test app. However, I need to use the latest dependencies so I can demonstrate that my changes do fix the reported issues. As a result, I have both fixes in the same PR.	2024-01-19 21:29:56 +00:00
Amanda Johnston	9262f7da15	fix(datetime): do not animate to new value when multiple values in different months are set (#28847) ... Issue number: resolves #28602 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> We animate to the new date when the value is changed, but we do not account for multiple selection. This behavior is valuable for when the value is set asynchronously on a different month than what it shown. However, this is confusing when there are multiple dates selected in different months, because we do not reasonably know which date to animate to. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> Datetime no longer animates to the new value if more than one date is selected, and the selected dates aren't all in the same month. An alternative strategy would be to always animate unless one of the selected dates is in the month currently being viewed. However, this would still mean guessing at which value the user wants to see, which we are trying to avoid. Based on this PR: https://github.com/ionic-team/ionic-framework/pull/28605 ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Co-authored-by: Liam DeBeasi <liamdebeasi@users.noreply.github.com> --------- Co-authored-by: Liam DeBeasi <liamdebeasi@users.noreply.github.com>	2024-01-18 18:43:06 +00:00
Liam DeBeasi	c47a16d6c3	fix(datetime): enter closes keyboard when typing time (#28848) ... Issue number: resolves #28325 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> When typing the time into the date picker pressing "Enter" does not close the on-screen keyboard. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Pressing "Enter" closes the on-screen keyboard ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Test: ⚠️ While I have a test for this, please also test this on a physical Android device. 1. Go to `src/components/datetime/test/basic` 2. Open the time picker (in any of the date times) 3. Tap the time to open the keyboard 4. Press "Enter" on Android. Observe that the keyboard closes. Dev build: `7.6.6-dev.11705528328.1ef5e17b`	2024-01-18 18:15:22 +00:00
Liam DeBeasi	0847c2ac2c	fix(segment): setting value via binding updates button state (#28837) ... Issue number: resolves #28816 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> The value is set on Segment asynchronously when binding it in Angular. However, the timing works out such that the value changes after `connectedCallback` is fired but before any Stencil Watchers are configured. As a result, our `value` property watcher does not fire which causes `ionSelect` to not be emitted. Segment Buttons rely on this event to know when to update their state (if the value changes such that a segment button is now selected). This results in a checked segment button not appearing checked. This is similar to other issues that have been fixed: https://github.com/ionic-team/ionic-framework/pull/28510 https://github.com/ionic-team/ionic-framework/pull/28488 https://github.com/ionic-team/ionic-framework/pull/28526 ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Segment now emits `ionSelect` on `componentDidLoad` so that any descendant segment buttons can update correctly. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Dev build: `7.6.5-dev.11705415448.16878103` This is a timing issue with Stencil, so I am unable to write a reliable automated test. Reviewers should test the dev build in the repro provided in the linked issue.	2024-01-17 21:17:54 +00:00
Maria Hutt	ad65824722	fix(alert): remove border-right on ios stacked buttons (#28821) ... Issue number: internal --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> When iOS alert has 3 or more buttons, those are rendered vertically. All but the last button will have a right border. There shouldn't be a right border when the buttons are stacked.  ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Vertical buttons don't have a right border. - Separated the test in order to also test dark theme.   ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> N/A --------- Co-authored-by: ionitron <hi@ionicframework.com>	2024-01-17 17:12:07 +00:00
Liam DeBeasi	aed7a03532	fix(select): click handlers on slotted content fire (#28839) ... Issue number: resolves #28818 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> Select has logic in place to prevent the overlay from opening when clicking the slotted content. As part of this, we need to deal with the `<label>` element dispatching another click that then bubbles up and causes the overlay to open when clicking the slotted content. We currently deal with this by calling `preventDefault` which prevents this extra event from being dispatched only when clicking the slotted content. We also call `stopPropagation`. This code is not necessary, and in most cases should not have any adverse effects on developer applications. However, this does impact React applications due to how React handles events. When a developer places `onClick` on a slotted element, a native "click" listener is not immediately applied to that element. Instead, React adds a native "click" listener to the root element of an application. When that listener's callback fires, React will dispatch a synthetic click event on the slotted element. Since we are calling `stopPropagation`, the click event never bubbles up to this root node's listener. As a result, the synthetic event is never dispatched on the slotted element, and the developed `onClick` callback never fires. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Select no longer prevents events from bubbling. The existing `event.preventDefault` is sufficient to prevent the label from dispatching another click (thereby causing the select overlay to open) when clicking the slotted content. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Dev build: `7.6.5-dev.11705430252.1023daf3`	2024-01-17 17:07:11 +00:00
Liam DeBeasi	998870f55d	merge release-7.6.5 ... Release 7.6.5	2024-01-17 09:54:38 -05:00
Liam DeBeasi	0fb88315df	chore: update package lock	2024-01-17 09:41:15 -05:00
Liam DeBeasi	0860ea0951	chore: workflow pulls correct version of branch	2024-01-17 09:39:57 -05:00
Liam DeBeasi	71e485d770	chore: clean up changelog	2024-01-17 09:31:16 -05:00
ionitron	e2708ff651	v7.6.5 v7.6.5	2024-01-17 14:23:09 +00:00
dependabot[bot]	774872f671	chore(deps): Bump @stencil/core from 4.9.1 to 4.10.0 in /core (#28835) ... Bumps [@stencil/core](https://github.com/ionic-team/stencil) from 4.9.1 to 4.10.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/stencil/releases"><code>@​stencil/core</code>'s releases</a>.</em></p> <blockquote> <h2>🍪 v4.10.0 (2024-01-15)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>runtime:</strong> revert slot relocation forwarding (<a href="https://redirect.github.com/ionic-team/stencil/issues/5222">#5222</a>) (<a href="a2e119d059">a2e119d</a>)</li> <li><strong>runtime:</strong> slot regressions from experimental slot fixes (<a href="https://redirect.github.com/ionic-team/stencil/issues/5221">#5221</a>) (<a href="3b4deaabb6">3b4deaa</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>deps:</strong> update dependency typescript to ~5.3.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5248">#5248</a>) (<a href="e0e6a9629e">e0e6a96</a>)</li> <li><strong>runtime:</strong> add extras flag for scoped slot changes (<a href="https://redirect.github.com/ionic-team/stencil/issues/5220">#5220</a>) (<a href="15ff9509a4">15ff950</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ionic-team/stencil/blob/main/CHANGELOG.md"><code>@​stencil/core</code>'s changelog</a>.</em></p> <blockquote> <h1>🍪 <a href="https://github.com/ionic-team/stencil/compare/v4.9.1...v4.10.0">4.10.0</a> (2024-01-15)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>runtime:</strong> revert slot relocation forwarding (<a href="https://redirect.github.com/ionic-team/stencil/issues/5222">#5222</a>) (<a href="a2e119d059">a2e119d</a>)</li> <li><strong>runtime:</strong> slot regressions from experimental slot fixes (<a href="https://redirect.github.com/ionic-team/stencil/issues/5221">#5221</a>) (<a href="3b4deaabb6">3b4deaa</a>)</li> </ul> <h3>Features</h3> <ul> <li><strong>deps:</strong> update dependency typescript to ~5.3.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5248">#5248</a>) (<a href="e0e6a9629e">e0e6a96</a>)</li> <li><strong>runtime:</strong> add extras flag for scoped slot changes (<a href="https://redirect.github.com/ionic-team/stencil/issues/5220">#5220</a>) (<a href="15ff9509a4">15ff950</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="13c7b7d881"><code>13c7b7d</code></a> v4.10.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5261">#5261</a>)</li> <li><a href="09ed20193b"><code>09ed201</code></a> chore(repo): prevent renovate from upgrating open (<a href="https://redirect.github.com/ionic-team/stencil/issues/5218">#5218</a>)</li> <li><a href="22c08d5b1d"><code>22c08d5</code></a> chore(deps): update dependency ws to v8.16.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5217">#5217</a>)</li> <li><a href="8b4d18efcc"><code>8b4d18e</code></a> chore(deps): update dependency eslint-plugin-jsdoc to v48 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5260">#5260</a>)</li> <li><a href="4e1444543c"><code>4e14445</code></a> chore(deps): update dependency <code>@​types/node</code> to v20.11.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5256">#5256</a>)</li> <li><a href="a76fb5c0c9"><code>a76fb5c</code></a> chore(deps): update node.js to v20.11.0 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5258">#5258</a>)</li> <li><a href="91d7d49a9b"><code>91d7d49</code></a> chore(deps): update dependency eslint-plugin-jest to v27.6.2 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5255">#5255</a>)</li> <li><a href="1d72708429"><code>1d72708</code></a> chore(deps): update dependency dts-bundle-generator to v9.2.4 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5254">#5254</a>)</li> <li><a href="79211ddf5f"><code>79211dd</code></a> chore(deps): update dependency <code>@​types/eslint</code> to v8.56.2 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5253">#5253</a>)</li> <li><a href="7e96b34cd7"><code>7e96b34</code></a> chore(deps): update dependency postcss to v8.4.33 (<a href="https://redirect.github.com/ionic-team/stencil/issues/5236">#5236</a>)</li> <li>Additional commits viewable in <a href="https://github.com/ionic-team/stencil/compare/v4.9.1...v4.10.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-16 16:55:33 +00:00
Liam DeBeasi	fb7735397e	fix(angular): add old IonBackButtonDelegate import (#28831) ... Issue number: resolves #28827 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> This import was renamed to `IonBackButton` as part of 9f20780d66. However, we did not consider that some developers are importing this to use with `ViewChild`. While we should keep alignment with other component imports, we need to support the old import until we can make a breaking change in Ionic 8. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Adds the old IonBackButtonDelegate import ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Dev build: `7.6.5-dev.11705352188.1c6cdb08`	2024-01-16 16:53:25 +00:00
Amanda Johnston	dbaaa5bd9f	fix(list): remove uneeded border radius from items in inset list (#28830) ... Issue number: N/A --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> In MD mode, items in an inset list currently receive their own border radius, separate from the border radius also applied to the inset list itself. The original intent was likely to ensure that the corners of the items don't spill out of the list. However, the item's border radius is no longer needed, for two reasons: 1. MD has since added top/bottom padding to their lists ([spec](https://m2.material.io/components/lists#specs)), which we've mirrored. This means the borders no longer line up anyway. 2. Even if a developer removes the list's vertical padding (we set it on the host [here](535b8ed724/core/src/components/list/list.md.scss (L9)), so it's easy to overwrite), inset lists currently have `overflow: hidden` set [here](535b8ed724/core/src/components/list/list.scss (L20)), so the list's border radius still applies correctly even with the items' border radius removed. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> Item border radius in inset lists removed. When testing locally, you may find it useful to increase the MD border radius value [here](535b8ed724/core/src/components/list/list.md.vars.scss (L47)) so it's easier to see. ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 3. Update the BREAKING.md file with the breaking change. 4. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->	2024-01-16 16:31:28 +00:00
dependabot[bot]	b7adede05a	chore(deps-dev): Bump @axe-core/playwright from 4.8.2 to 4.8.3 in /core (#28834) ... Bumps [@axe-core/playwright](https://github.com/dequelabs/axe-core-npm) from 4.8.2 to 4.8.3. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/dequelabs/axe-core-npm/blob/develop/CHANGELOG.md"><code>@​axe-core/playwright</code>'s changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/dequelabs/axe-core-npm/compare/v4.8.1...v4.8.3">4.8.3</a> (2024-01-09)</h2> <h3>Bug Fixes</h3> <ul> <li>allow cjs version of packages to export a default value (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/943">#943</a>) (<a href="b5aee3424f">b5aee34</a>)</li> <li>Update axe-core to v4.8.3 (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/968">#968</a>) (<a href="be9002c518">be9002c</a>)</li> <li>Update axe-core to v4.8.3 (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/978">#978</a>) (<a href="1c837404aa">1c83740</a>)</li> <li><strong>webdriverio:</strong> fix types between v8 and &lt;v8 (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/962">#962</a>) (<a href="0511338017">0511338</a>)</li> <li><strong>webdriverio:</strong> work with <code>@​wdio/globals</code> (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/882">#882</a>) (<a href="2e016b4e17">2e016b4</a>)</li> <li><strong>webdriverjs:</strong> fix default commonJs export (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/927">#927</a>) (<a href="b07d38cc2d">b07d38c</a>)</li> </ul> <h3>Reverts</h3> <ul> <li>Revert &quot;fix: Update axe-core to v4.8.3 (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/968">#968</a>)&quot; (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/977">#977</a>) (<a href="0aff5d86e5">0aff5d8</a>), closes <a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/968">#968</a> <a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/977">#977</a></li> <li>Revert &quot;chore: merge master into develop (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/955">#955</a>)&quot; (<a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/956">#956</a>) (<a href="07e7d9e7e1">07e7d9e</a>), closes <a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/955">#955</a> <a href="https://redirect.github.com/dequelabs/axe-core-npm/issues/956">#956</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/dequelabs/axe-core-npm/commits">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>	2024-01-16 15:02:19 +00:00
Maria Hutt	33aa8e36d9	chore(alert): remove ion-buttons from tests (#28823) ... Issue number: internal --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> `ion-button` is being used as a way to open the alerts. It's not being used to test functionality. When `ion-button` is updated then the screenshots in the alert tests must be updated. This shouldn't happen when `ion-button` isn't necessary to have in these tests. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Replaced `ion-button` with `button` ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> N/A --------- Co-authored-by: ionitron <hi@ionicframework.com>	2024-01-15 22:05:46 +00:00
Liam DeBeasi	535b8ed724	chore(ci): use correct github credentials for pushing (#28806) ... The update-package-lock job did not configure Git credentials correctly. As a result, the job is unable to push the `package-lock.json` changes to the repo: https://github.com/ionic-team/ionic-framework/actions/runs/7476310958/job/20346663176 This PR configures the job with the correct credentials.	2024-01-10 16:47:44 +00:00