mirror of
https://github.com/ionic-team/ionic-framework.git
synced 2025-11-07 23:16:52 +08:00
5e55bef3bc
Bumps [@playwright/test](https://github.com/Microsoft/playwright) from 1.32.3 to 1.33.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Microsoft/playwright/releases"><code>@playwright/test</code>'s releases</a>.</em></p> <blockquote> <h2>v1.33.0</h2> <h3>Locators Update</h3> <ul> <li> <p>Use [<code>locator.or()</code>] to create a locator that matches either of the two locators. Consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead. In this case, you can wait for either a "New email" button, or a dialog and act accordingly:</p> <pre lang="js"><code>const newEmail = page.getByRole('button', { name: 'New' }); const dialog = page.getByText('Confirm security settings'); await expect(newEmail.or(dialog)).toBeVisible(); if (await dialog.isVisible()) await page.getByRole('button', { name: 'Dismiss' }).click(); await newEmail.click(); </code></pre> </li> <li> <p>Use new options <code>hasNot</code> and <code>hasNotText</code> in [<code>locator.filter()</code>] to find elements that <strong>do not match</strong> certain conditions.</p> <pre lang="js"><code>const rowLocator = page.locator('tr'); await rowLocator .filter({ hasNotText: 'text in column 1' }) .filter({ hasNot: page.getByRole('button', { name: 'column 2 button' }) }) .screenshot(); </code></pre> </li> <li> <p>Use new web-first assertion [<code>locatorAssertions.toBeAttached()</code>] to ensure that the element is present in the page's DOM. Do not confuse with the [<code>locatorAssertions.toBeVisible()</code>] that ensures that element is both attached & visible.</p> </li> </ul> <h3>New APIs</h3> <ul> <li>[<code>locator.or()</code>]</li> <li>New option <code>hasNot</code> in [<code>locator.filter()</code>]</li> <li>New option <code>hasNotText</code> in [<code>locator.filter()</code>]</li> <li>[<code>locatorAssertions.toBeAttached()</code>]</li> <li>New option <code>timeout</code> in [<code>route.fetch()</code>]</li> <li>[<code>reporter.onExit()</code>]</li> </ul> <h3>⚠️ Breaking change</h3> <ul> <li>The <code>mcr.microsoft.com/playwright:v1.33.0</code> now serves a Playwright image based on Ubuntu Jammy. To use the focal-based image, please use <code>mcr.microsoft.com/playwright:v1.33.0-focal</code> instead.</li> </ul> <h3>Browser Versions</h3> <ul> <li>Chromium 113.0.5672.53</li> <li>Mozilla Firefox 112.0</li> <li>WebKit 16.4</li> </ul> <p>This version was also tested against the following stable channels:</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="b64516e146"><code>b64516e</code></a> cherry-pick(<a href="https://redirect.github.com/Microsoft/playwright/issues/22673">#22673</a>): devops: fix workflow publishing</li> <li><a href="2ca4cd018f"><code>2ca4cd0</code></a> cherry-pick(<a href="https://redirect.github.com/Microsoft/playwright/issues/22667">#22667</a>): chore(chromium): remove --disable-sync CLI switch</li> <li><a href="0d61e314f6"><code>0d61e31</code></a> chore: mark 1.33.0 (<a href="https://redirect.github.com/Microsoft/playwright/issues/22602">#22602</a>)</li> <li><a href="64bca2269b"><code>64bca22</code></a> cherry-pick(<a href="https://redirect.github.com/Microsoft/playwright/issues/22615">#22615</a>): docs: release notes 1.33</li> <li><a href="9a3c4e45e3"><code>9a3c4e4</code></a> cherry-pick(<a href="https://redirect.github.com/Microsoft/playwright/issues/22628">#22628</a>): docs: add UI mode doc (<a href="https://redirect.github.com/Microsoft/playwright/issues/22632">#22632</a>)</li> <li><a href="adef765405"><code>adef765</code></a> cherry-pick(<a href="https://redirect.github.com/Microsoft/playwright/issues/22609">#22609</a>): chore: fix list-files</li> <li><a href="eed6c33283"><code>eed6c33</code></a> feat(webkit): roll to r1837 (<a href="https://redirect.github.com/Microsoft/playwright/issues/22566">#22566</a>)</li> <li><a href="05b113f050"><code>05b113f</code></a> docs: add warning to locator.all (<a href="https://redirect.github.com/Microsoft/playwright/issues/22537">#22537</a>)</li> <li><a href="62bd41912d"><code>62bd419</code></a> chore: cleanup bandaid firefox pref (<a href="https://redirect.github.com/Microsoft/playwright/issues/22570">#22570</a>)</li> <li><a href="99d4887053"><code>99d4887</code></a> feat(firefox): roll to r1403 (<a href="https://redirect.github.com/Microsoft/playwright/issues/22540">#22540</a>)</li> <li>Additional commits viewable in <a href="https://github.com/Microsoft/playwright/compare/v1.32.3...v1.33.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 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> Co-authored-by: Liam DeBeasi <liamdebeasi@users.noreply.github.com> Co-authored-by: ionitron <hi@ionicframework.com>
Ionic
Ionic is an open source app development toolkit for building modern, fast, top-quality cross-platform native and Progressive Web Apps from a single codebase with JavaScript and the Web.
Ionic is based on Web Components, which enables significant performance, usability, and feature improvements alongside support for popular web frameworks like Angular, React, and Vue.
Quickstart
·
Documentation
·
Contribute
·
Blog
Community:
Discord
·
Forums
·
Twitter
Packages
| Project | Package | Version | Downloads | Links |
|---|---|---|---|---|
| Core | @ionic/core |
 |
 |
README.md |
| Angular | @ionic/angular |
 |
 |
README.md |
| Vue | @ionic/vue |
 |
 |
README.md |
| React | @ionic/react |
 |
 |
README.md |
Looking for the ionic-angular package? Ionic 3 has been moved to the ionic-v3 repo. See Earlier Versions.
Getting Started
Start a new project by following our quick Getting Started guide. We would love to hear from you! If you have any feedback or run into issues using our framework, please file an issue on this repository.
Migration Guides
Already have an Ionic app? These guides will help you migrate to the latest versions.
Examples
The Ionic Conference App is a full featured Ionic app. It is the perfect starting point for learning and building your own app.
Contributing
Thanks for your interest in contributing! Read up on our guidelines for contributing and then look through our issues with a help wanted label.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Future Goals
As Ionic Framework components migrate to the web component standard, a goal of ours is to have Ionic Framework easily work within all of the popular frameworks.
Earlier Versions
The source code for earlier versions of the Ionic Framework may exist in other repositories. Please open issues and pull requests in their respective repositories.
- Ionic 2/3: Moved to
ionic-team/ionic-v3 - Ionic 1: Moved to
ionic-team/ionic-v1