Release 8.0.2 #29432
Merged
Release 8.0.2 #29432
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR removes the v5 and v4 lts tags from the release scripts. The main branch should always be used to deploy to the latest/next tags and never in the past. Instead, the version branches have the option to deploy to their respective LTS tags.
The ticket was marked as done, but this one was missed.
Issue number: N/A --------- ## What is the current behavior? Currently, every Sass variable in Ionic has the `!default` flag added to the end. From the [Sass variables documentation](https://sass-lang.com/documentation/variables/): > Normally when you assign a value to a variable, if that variable already had a value, its old value is overwritten. But if you’re writing a Sass library, you might want to allow your users to configure your library’s variables before you use them to generate CSS. > > To make this possible, Sass provides the `!default` flag. This assigns a value to a variable only if that variable isn’t defined or its value is [null](https://sass-lang.com/documentation/values/null). Otherwise, the existing value will be used. In past versions of Ionic Framework, developers wrote Sass variables to rebuild Ionic Framework using their own values. In the latest versions of Ionic Framework, this is not possible. ## What is the new behavior? Removes the `!default` flag from all Sass variables. ## Does this introduce a breaking change? - [ ] Yes - [x] No ------- Co-authored-by: brandyscarney <[email protected]>
…lue (#29407) Issue number: resolves ionic-team/ionic-docs#3588 --------- <!-- 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 documentation around `ionChange` not being emitted when programmatically changing the property associated to the "value" is either inconsistent or missing from certain components. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Adds the documentation to the missing components. - Makes the documentation consistent across components. ## 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/docs/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. -->
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | Type | Update | |---|---|---|---|---|---|---|---| | [@axe-core/playwright](https://togithub.com/dequelabs/axe-core-npm) | [`4.8.5` -> `4.9.0`](https://renovatebot.com/diffs/npm/@axe-core%2fplaywright/4.8.5/4.9.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | devDependencies | minor | | [@playwright/test](https://playwright.dev) ([source](https://togithub.com/microsoft/playwright)) | [`1.42.1` -> `1.43.1`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.42.1/1.43.1) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | devDependencies | minor | | mcr.microsoft.com/playwright | `v1.42.1` -> `v1.43.1` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | final | minor | --- ### Release Notes <details> <summary>dequelabs/axe-core-npm (@​axe-core/playwright)</summary> ### [`v4.9.0`](https://togithub.com/dequelabs/axe-core-npm/blob/HEAD/CHANGELOG.md#490-2024-04-01) [Compare Source](https://togithub.com/dequelabs/axe-core-npm/compare/v4.8.5...v4.9.0) ##### Bug Fixes - get correct new window handle with Selenium 3 workaround ([#​1031](https://togithub.com/dequelabs/axe-core-npm/issues/1031)) ([b72c735](https://togithub.com/dequelabs/axe-core-npm/commit/b72c73571c12c81c2ef3dc3ebe89e15769f0942b)), closes [#​1027](https://togithub.com/dequelabs/axe-core-npm/issues/1027) [/github.com/dequelabs/axe-core-maven-html/blob/ad58b26a8d0e2f1afed33b2c5cbca22b54644b99/selenium/src/main/java/com/deque/html/axecore/extensions/WebDriverExtensions.java#L126](https://togithub.com//github.com/dequelabs/axe-core-maven-html/blob/ad58b26a8d0e2f1afed33b2c5cbca22b54644b99/selenium/src/main/java/com/deque/html/axecore/extensions/WebDriverExtensions.java/issues/L126) [#​936](https://togithub.com/dequelabs/axe-core-npm/issues/936) ##### Features - Update axe-core to v4.9.0 ([#​1028](https://togithub.com/dequelabs/axe-core-npm/issues/1028)) ([7e152b6](https://togithub.com/dequelabs/axe-core-npm/commit/7e152b65ff30b9e1cb26c3b0564457b32a0d35b2)) #### [4.8.5](https://togithub.com/dequelabs/axe-core-npm/compare/v4.8.4...v4.8.5) (2024-02-08) ##### Bug Fixes - Update axe-core to v4.8.4 ([#​1008](https://togithub.com/dequelabs/axe-core-npm/issues/1008)) ([d54f145](https://togithub.com/dequelabs/axe-core-npm/commit/d54f145a4078c4730a850e694c9eb77297c23a35)) #### [4.8.4](https://togithub.com/dequelabs/axe-core-npm/compare/v4.8.3...v4.8.4) (2024-01-23) ##### Bug Fixes - **webdriverjs:** use new headless argument to fix [email protected] breaking release ([#​992](https://togithub.com/dequelabs/axe-core-npm/issues/992)) ([0daba98](https://togithub.com/dequelabs/axe-core-npm/commit/0daba98684ede79bfb6488dd1b81f7d863e69d99)) #### [4.8.3](https://togithub.com/dequelabs/axe-core-npm/compare/v4.8.1...v4.8.3) (2024-01-09) ##### Bug Fixes - allow cjs version of packages to export a default value ([#​943](https://togithub.com/dequelabs/axe-core-npm/issues/943)) ([b5aee34](https://togithub.com/dequelabs/axe-core-npm/commit/b5aee3424fe4d0fbc0b2065e9c0bc56ce4032755)) - Update axe-core to v4.8.3 ([#​968](https://togithub.com/dequelabs/axe-core-npm/issues/968)) ([be9002c](https://togithub.com/dequelabs/axe-core-npm/commit/be9002c518b335f56fa21e1bff99e07281be814b)) - Update axe-core to v4.8.3 ([#​978](https://togithub.com/dequelabs/axe-core-npm/issues/978)) ([1c83740](https://togithub.com/dequelabs/axe-core-npm/commit/1c837404aa2a63fb6be6f04760d1faec886bc5dc)) - **webdriverio:** fix types between v8 and \<v8 ([#​962](https://togithub.com/dequelabs/axe-core-npm/issues/962)) ([0511338](https://togithub.com/dequelabs/axe-core-npm/commit/0511338017f52fba78c6ff3708f0c9e950e7a34e)) - **webdriverio:** work with [@​wdio/globals](https://togithub.com/wdio/globals) ([#​882](https://togithub.com/dequelabs/axe-core-npm/issues/882)) ([2e016b4](https://togithub.com/dequelabs/axe-core-npm/commit/2e016b4e17cff09f158427862f2fd2134a62cbc6)) - **webdriverjs:** fix default commonJs export ([#​927](https://togithub.com/dequelabs/axe-core-npm/issues/927)) ([b07d38c](https://togithub.com/dequelabs/axe-core-npm/commit/b07d38cc2d85c6127391686482abf762758dce34)) ##### Reverts - Revert "fix: Update axe-core to v4.8.3 ([#​968](https://togithub.com/dequelabs/axe-core-npm/issues/968))" ([#​977](https://togithub.com/dequelabs/axe-core-npm/issues/977)) ([0aff5d8](https://togithub.com/dequelabs/axe-core-npm/commit/0aff5d86e539cb9054bc3bd62a2f2cba8a716b3e)), closes [#​968](https://togithub.com/dequelabs/axe-core-npm/issues/968) [#​977](https://togithub.com/dequelabs/axe-core-npm/issues/977) - Revert "chore: merge master into develop ([#​955](https://togithub.com/dequelabs/axe-core-npm/issues/955))" ([#​956](https://togithub.com/dequelabs/axe-core-npm/issues/956)) ([07e7d9e](https://togithub.com/dequelabs/axe-core-npm/commit/07e7d9e7e166391e4fe406db5dc541f56ca44514)), closes [#​955](https://togithub.com/dequelabs/axe-core-npm/issues/955) [#​956](https://togithub.com/dequelabs/axe-core-npm/issues/956) #### [4.8.2](https://togithub.com/dequelabs/axe-core-npm/compare/v4.8.1...v4.8.2) (2023-11-30) ##### Bug Fixes - allow cjs version of packages to export a default value ([#​943](https://togithub.com/dequelabs/axe-core-npm/issues/943)) ([b5aee34](https://togithub.com/dequelabs/axe-core-npm/commit/b5aee3424fe4d0fbc0b2065e9c0bc56ce4032755)) - **webdriverio:** work with [@​wdio/globals](https://togithub.com/wdio/globals) ([#​882](https://togithub.com/dequelabs/axe-core-npm/issues/882)) ([2e016b4](https://togithub.com/dequelabs/axe-core-npm/commit/2e016b4e17cff09f158427862f2fd2134a62cbc6)) - **webdriverjs:** fix default commonJs export ([#​927](https://togithub.com/dequelabs/axe-core-npm/issues/927)) ([b07d38c](https://togithub.com/dequelabs/axe-core-npm/commit/b07d38cc2d85c6127391686482abf762758dce34)) #### [4.8.1](https://togithub.com/dequelabs/axe-core-npm/compare/v4.7.3...v4.8.1) (2023-10-11) ##### Bug Fixes - **cli:** better error message for ChromeDriver version mismatch ([#​680](https://togithub.com/dequelabs/axe-core-npm/issues/680)) ([10cf350](https://togithub.com/dequelabs/axe-core-npm/commit/10cf3509449587a14799fb168678258249bc1900)), closes [#​679](https://togithub.com/dequelabs/axe-core-npm/issues/679) - **cli:** improve error message on script timeout ([#​681](https://togithub.com/dequelabs/axe-core-npm/issues/681)) ([b407c6c](https://togithub.com/dequelabs/axe-core-npm/commit/b407c6cf1f8a980fc036b75c7b3f7198d3bb556c)) - **cli:** include required files when publishing ([#​851](https://togithub.com/dequelabs/axe-core-npm/issues/851)) ([3f1ff4b](https://togithub.com/dequelabs/axe-core-npm/commit/3f1ff4bd464215ce2eb1a243907872aaceadd21f)) - **cli:** respect --exit regardless of other flags ([#​750](https://togithub.com/dequelabs/axe-core-npm/issues/750)) ([bfa2328](https://togithub.com/dequelabs/axe-core-npm/commit/bfa232800d553d870933e5dfa26d669d2d566c08)) - pin axe-core version to accept patch updates only ([#​838](https://togithub.com/dequelabs/axe-core-npm/issues/838)) ([2456ed6](https://togithub.com/dequelabs/axe-core-npm/commit/2456ed641781c2262bf71db24f7f97755422d5f6)) - skip unloaded iframes for all apis ([#​752](https://togithub.com/dequelabs/axe-core-npm/issues/752)) ([0b15629](https://togithub.com/dequelabs/axe-core-npm/commit/0b15629ac12613d9cdfec9f102ff1e3922d28ac2)) ##### Features - **cli:** add --chrome-path option ([#​700](https://togithub.com/dequelabs/axe-core-npm/issues/700)) ([#​704](https://togithub.com/dequelabs/axe-core-npm/issues/704)) ([ada5d28](https://togithub.com/dequelabs/axe-core-npm/commit/ada5d28ccbbf9121f9d1fb5172347019c2ae63d1)) - **react:** export `logToConsole` fn ([#​812](https://togithub.com/dequelabs/axe-core-npm/issues/812)) ([480fb12](https://togithub.com/dequelabs/axe-core-npm/commit/480fb1268ffa3547a8d056a7c274607fca3ca274)) - Update axe-core to v4.8.2 ([#​835](https://togithub.com/dequelabs/axe-core-npm/issues/835)) ([2ac1eaf](https://togithub.com/dequelabs/axe-core-npm/commit/2ac1eafa6318453003ccfd7c33625e63725a7c00)) </details> <details> <summary>microsoft/playwright (@​playwright/test)</summary> ### [`v1.43.1`](https://togithub.com/microsoft/playwright/releases/tag/v1.43.1) [Compare Source](https://togithub.com/microsoft/playwright/compare/v1.43.0...v1.43.1) ##### Highlights [https://github.com/microsoft/playwright/issues/30300](https://togithub.com/microsoft/playwright/issues/30300) - \[REGRESSION]: UI mode restarts if keep storage state[https://github.com/microsoft/playwright/issues/30339](https://togithub.com/microsoft/playwright/issues/30339)9 - \[REGRESSION]: Brand new install of playwright, unable to run chromium with show browser using vscode ##### Browser Versions - Chromium 124.0.6367.29 - Mozilla Firefox 124.0 - WebKit 17.4 This version was also tested against the following stable channels: - Google Chrome 123 - Microsoft Edge 123 ### [`v1.43.0`](https://togithub.com/microsoft/playwright/releases/tag/v1.43.0) [Compare Source](https://togithub.com/microsoft/playwright/compare/v1.42.1...v1.43.0) #### New APIs - Method [browserContext.clearCookies()](https://playwright.dev/docs/api/class-browsercontext#browser-context-clear-cookies) now supports filters to remove only some cookies. ```js // Clear all cookies. await context.clearCookies(); // New: clear cookies with a particular name. await context.clearCookies({ name: 'session-id' }); // New: clear cookies for a particular domain. await context.clearCookies({ domain: 'my-origin.com' }); ``` - New mode `retain-on-first-failure` for [testOptions.trace](https://playwright.dev/docs/api/class-testoptions#test-options-trace). In this mode, trace is recorded for the first run of each test, but not for retires. When test run fails, the trace file is retained, otherwise it is removed. ```js title=playwright.config.ts import { defineConfig } from '@​playwright/test'; export default defineConfig({ use: { trace: 'retain-on-first-failure', }, }); ``` - New property [testInfo.tags](https://playwright.dev/docs/api/class-testinfo#test-info-tags) exposes test tags during test execution. ```js test('example', async ({ page }) => { console.log(test.info().tags); }); ``` - New method [locator.contentFrame()](https://playwright.dev/docs/api/class-locator#locator-content-frame) converts a `Locator` object to a `FrameLocator`. This can be useful when you have a `Locator` object obtained somewhere, and later on would like to interact with the content inside the frame. ```js const locator = page.locator('iframe[name="embedded"]'); // ... const frameLocator = locator.contentFrame(); await frameLocator.getByRole('button').click(); ``` - New method [frameLocator.owner()](https://playwright.dev/docs/api/class-framelocator#frame-locator-owner) converts a `FrameLocator` object to a `Locator`. This can be useful when you have a `FrameLocator` object obtained somewhere, and later on would like to interact with the `iframe` element. ```js const frameLocator = page.frameLocator('iframe[name="embedded"]'); // ... const locator = frameLocator.owner(); await expect(locator).toBeVisible(); ``` #### UI Mode Updates  - See tags in the test list. - Filter by tags by typing `@fast` or clicking on the tag itself. - New shortcuts: - <kbd>F5</kbd> to run tests. - <kbd>Shift</kbd> <kbd>F5</kbd> to stop running tests. - <kbd>Ctrl</kbd> <kbd>\`</kbd> to toggle test output. #### Browser Versions - Chromium 124.0.6367.29 - Mozilla Firefox 124.0 - WebKit 17.4 This version was also tested against the following stable channels: - Google Chrome 123 - Microsoft Edge 123 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "every weekday before 11am" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Never, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/ionic-team/ionic-framework). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yNjkuMiIsInVwZGF0ZWRJblZlciI6IjM3LjMyMS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Issue number: resolves #29386 --------- <!-- 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 item border does not have sufficient contrast in dark mode making the border almost invisible. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Removed the `--ion-border-color` in the MD dark palette. Instead, we're using the [theme default](https://github.com/ionic-team/ionic-framework/blob/dc1172a8411f71227b713a6d7addca91537ea438/core/src/themes/ionic.theme.default.md.scss#L31). ## 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/docs/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. --> The earliest reference to the offending line Brandy and I could find was [here](#18713 (comment)).
…ine (#29408) Issue number: resolves #29321 --------- <!-- 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 using a select with `fill="outline"`, `interface="popover"` and a width that fits the content of the options, the select options are not visible. The hidden radio is covering the text of the radio text options. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Select options are visible and no longer covered by the hidden radio container ## 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/docs/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: `8.0.2-dev.11714165638.13e7dd5b` Reproduction (issue): https://stackblitz.com/edit/angular-mndtkr Reproduction (with dev-build): https://stackblitz.com/edit/angular-mndtkr-d7wsnp Reproduction steps: 1. Open the select 2. Observe: The popover displays the options, but the options are not visible/readable to the user 3. Use the dev-build 4. Open the select 5. Observe: The popover displays the options and they are visible/readable to the user (5, 10, 15).
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@capacitor/core](https://capacitorjs.com) ([source](https://togithub.com/ionic-team/capacitor)) | [`^5.7.0` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@capacitor%2fcore/5.7.5/6.0.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [@capacitor/haptics](https://togithub.com/ionic-team/capacitor-plugins) | [`^5.0.7` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@capacitor%2fhaptics/5.0.7/6.0.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [@capacitor/keyboard](https://togithub.com/ionic-team/capacitor-plugins) | [`^5.0.8` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@capacitor%2fkeyboard/5.0.8/6.0.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | | [@capacitor/status-bar](https://togithub.com/ionic-team/capacitor-plugins) | [`^5.0.7` -> `^6.0.0`](https://renovatebot.com/diffs/npm/@capacitor%2fstatus-bar/5.0.7/6.0.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>ionic-team/capacitor (@​capacitor/core)</summary> ### [`v6.0.0`](https://togithub.com/ionic-team/capacitor/blob/HEAD/CHANGELOG.md#600-2024-04-15) [Compare Source](https://togithub.com/ionic-team/capacitor/compare/5.7.5...6.0.0) ##### Bug Fixes - **cli:** Change Capacitor plugin files check ([#​7375](https://togithub.com/ionic-team/capacitor/issues/7375)) ([fbfb778](https://togithub.com/ionic-team/capacitor/commit/fbfb77825fdd3343e85868ea28b8e14a482dcf4a)) - **cli:** Don't downgrade gradle version on migrate ([#​7385](https://togithub.com/ionic-team/capacitor/issues/7385)) ([c79211e](https://togithub.com/ionic-team/capacitor/commit/c79211ec9dde81a57aca5cee8ab09cdef0c9ad86)) - **cli:** Removing extra dash in android apk name flavor parsing ([#​7382](https://togithub.com/ionic-team/capacitor/issues/7382)) ([3c411fd](https://togithub.com/ionic-team/capacitor/commit/3c411fd0a400b18c2d032e3b8be3fc4b5449bcbd)) - **http:** Add URLSearchParams support ([#​7374](https://togithub.com/ionic-team/capacitor/issues/7374)) ([9367ecc](https://togithub.com/ionic-team/capacitor/commit/9367ecc56a0c78249dccdf95dca5006422144289)) - **http:** prevent POST request from being proxied ([#​7395](https://togithub.com/ionic-team/capacitor/issues/7395)) ([7b8c352](https://togithub.com/ionic-team/capacitor/commit/7b8c3523decd5610dcf09e926640bf35b382d61d)) - secure cookies often are not set by the cookie plugin ([#​7261](https://togithub.com/ionic-team/capacitor/issues/7261)) ([cda1886](https://togithub.com/ionic-team/capacitor/commit/cda18861aea3ced7835f959cba612cea98761c58)) ##### Features - **cli:** Support bun when running cap migrate ([#​7386](https://togithub.com/ionic-team/capacitor/issues/7386)) ([3f96ff9](https://togithub.com/ionic-team/capacitor/commit/3f96ff911588c517dc2d924f55ef28a25c30bd33)) </details> <details> <summary>ionic-team/capacitor-plugins (@​capacitor/haptics)</summary> ### [`v6.0.0`](https://togithub.com/ionic-team/capacitor-plugins/releases/tag/%40capacitor/share%406.0.0) [Compare Source](https://togithub.com/ionic-team/capacitor-plugins/compare/@capacitor/[email protected]...@capacitor/[email protected]) **Note:** Version bump only for package [@​capacitor/share](https://togithub.com/capacitor/share) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "every weekday before 11am" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Never, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/ionic-team/ionic-framework). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zMDEuNCIsInVwZGF0ZWRJblZlciI6IjM3LjMyMS4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Issue number: resolves #29393 --------- <!-- 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. --> With Stencil v4.17.1, in Angular apps Stencil's `MockDoc` will be bundled with the consumer's code resulting in a significant increase to the main chunk. |v8.0.0| |---| || |v8.0.1| |---| || ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Updates to v4.17.2 of Stencil, which resolves this regression 🎉 |Dev-build| |---| || ## 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/docs/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: `8.0.2-dev.11714402065.169342dc`
Issue number: resolves #29198 --------- <!-- 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 #27917 I failed to account for RTL. This caused the navigation with the arrow buttons to break because the scroll position was always < 2. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Datetime now checks if the component is in RTL mode when creating the scrollLeft threshold. ## 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/docs/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. -->
#29327) Issue number: resolves #28751 --------- <!-- 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 large title transition does not account for back buttons with no text value. We assume that the [`.button-text` element ](https://github.com/ionic-team/ionic-framework/blob/bfaf528e61fd82c9106e3c5060921fb79d97156a/core/src/components/back-button/back-button.tsx#L168) is always defined, but that is not the case when `text=""` on the back button. As a result, devs were getting errors because we tried to get the bounding box of a undefined. ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - Revised the large title logic to only grab values from the back button text if the back button text element is actually defined There should be **no behavior change** when the back button text element is defined. ## 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/docs/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.8.5-dev.11713282122.18cabf98`⚠️ Reviewers: Please test this in the sample application on the linked issue. Please be sure to test the following conditions: 1. When the back button text is defined 2. When the back button text is not defined 3. With the default font scale 4. With a larger font scale
This PR makes the following changes: 1. Clarifies when `.ion-focusable` should be used versus `:focus-visible`. 2. Clarifies that `Locator` needs to be typecast when using `Locator.spyOnEvent`.
github-actions
bot
added
package: core
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
](https://renovatebot.com){kind=link}
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: resolves #
What is the current behavior?
What is the new behavior?
Does this introduce a breaking change?
Other information