b8b5984150
Merge branch 'main' into chore-merge-main-into-next
2025-03-18 18:05:14 -04:00
c63ec2e98d
chore(deps): update playwright ( #29840 )
...
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence | Type |
Update |
|---|---|---|---|---|---|---|---|
|
[@axe-core/playwright](https://redirect.github.com/dequelabs/axe-core-npm )
| [`^4.10.0` ->
`^4.10.1`](https://renovatebot.com/diffs/npm/@axe-core%2fplaywright/4.10.0/4.10.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 | patch |
| [@playwright/test](https://playwright.dev )
([source](https://redirect.github.com/microsoft/playwright )) |
[`^1.46.1` ->
`^1.51.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.46.1/1.51.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 |
| mcr.microsoft.com/playwright | `v1.46.1` -> `v1.51.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/ )
| final | minor |
---
### Release Notes
<details>
<summary>dequelabs/axe-core-npm (@​axe-core/playwright)</summary>
###
[`v4.10.1`](https://redirect.github.com/dequelabs/axe-core-npm/blob/HEAD/CHANGELOG.md#4101-2024-10-29 )
[Compare
Source](https://redirect.github.com/dequelabs/axe-core-npm/compare/v4.10.0...v4.10.1 )
##### Bug Fixes
- Update axe-core to v4.10.1
([#​1124](https://redirect.github.com/dequelabs/axe-core-npm/issues/1124 ))
([099818b](099818bcef ))
- Update axe-core to v4.10.2
([#​1128](https://redirect.github.com/dequelabs/axe-core-npm/issues/1128 ))
([aaaa34e](aaaa34e7c3 ))
</details>
<details>
<summary>microsoft/playwright (@​playwright/test)</summary>
###
[`v1.51.0`](https://redirect.github.com/microsoft/playwright/compare/v1.50.1...3707a93754368ec1e0e2876767e8a9209f036f8a )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.50.1...v1.51.0 )
###
[`v1.50.1`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.50.1 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.50.0...v1.50.1 )
##### Highlights
[https://github.com/microsoft/playwright/issues/34483 ](https://redirect.github.com/microsoft/playwright/issues/34483 )
- \[Feature]: single aria snapshot for different
engines/browsers[https://github.com/microsoft/playwright/issues/34497 ](https://redirect.github.com/microsoft/playwright/issues/34497 )7
- \[Bug]: Firefox not handling keepalive: true fetch
request[https://github.com/microsoft/playwright/issues/34504 ](https://redirect.github.com/microsoft/playwright/issues/34504 )04
- \[Bug]: update snapshots not creating good
dif[https://github.com/microsoft/playwright/issues/34507 ](https://redirect.github.com/microsoft/playwright/issues/34507 )507
- \[Bug]: snapshotPathTemplate doesnt work when multiple
proje[https://github.com/microsoft/playwright/issues/34462 ](https://redirect.github.com/microsoft/playwright/issues/34462 )4462
- \[Bug]: updateSnapshots "changed" throws an error
#### Browser Versions
- Chromium 133.0.6943.16
- Mozilla Firefox 134.0
- WebKit 18.2
This version was also tested against the following stable channels:
- Google Chrome 132
- Microsoft Edge 132
###
[`v1.50.0`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.50.0 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.49.1...v1.50.0 )
#### Test runner
- New option
[`timeout`](https://playwright.dev/docs/api/class-test#test-step-option-timeout )
allows specifying a maximum run time for an individual test step. A
timed-out step will fail the execution of the test.
```js
test('some test', async ({ page }) => {
await test.step('a step', async () => {
// This step can time out separately from the test
}, { timeout: 1000 });
});
```
- New method
[test.step.skip()](https://playwright.dev/docs/api/class-test#test-step-skip )
to disable execution of a test step.
```js
test('some test', async ({ page }) => {
await test.step('before running step', async () => {
// Normal step
});
await test.step.skip('not yet ready', async () => {
// This step is skipped
});
await test.step('after running step', async () => {
// This step still runs even though the previous one was skipped
});
});
```
- Expanded
[expect(locator).toMatchAriaSnapshot()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-match-aria-snapshot-2 )
to allow storing of aria snapshots in separate YAML files.
- Added method
[expect(locator).toHaveAccessibleErrorMessage()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-have-accessible-error-message )
to assert the Locator points to an element with a given [aria
errormessage](https://w3c.github.io/aria/#aria-errormessage ).
- Option
[testConfig.updateSnapshots](https://playwright.dev/docs/api/class-testconfig#test-config-update-snapshots )
added the configuration enum `changed`. `changed` updates only the
snapshots that have changed, whereas `all` now updates all snapshots,
regardless of whether there are any differences.
- New option
[testConfig.updateSourceMethod](https://playwright.dev/docs/api/class-testconfig#test-config-update-source-method )
defines the way source code is updated when
[testConfig.updateSnapshots](https://playwright.dev/docs/api/class-testconfig#test-config-update-snapshots )
is configured. Added `overwrite` and `3-way` modes that write the
changes into source code, on top of existing `patch` mode that creates a
patch file.
```bash
npx playwright test --update-snapshots=changed
--update-source-method=3way
```
- Option
[testConfig.webServer](https://playwright.dev/docs/api/class-testconfig#test-config-web-server )
added a `gracefulShutdown` field for specifying a process kill signal
other than the default `SIGKILL`.
- Exposed
[testStep.attachments](https://playwright.dev/docs/api/class-teststep#test-step-attachments )
from the reporter API to allow retrieval of all attachments created by
that step.
- New option `pathTemplate` for `toHaveScreenshot` and
`toMatchAriaSnapshot` assertions in the
[testConfig.expect](https://playwright.dev/docs/api/class-testconfig#test-config-expect )
configuration.
#### UI updates
- Updated default HTML reporter to improve display of attachments.
- New button for picking elements to produce aria snapshots.
- Additional details (such as keys pressed) are now displayed alongside
action API calls in traces.
- Display of `canvas` content in traces is error-prone. Display is now
disabled by default, and can be enabled via the `Display canvas content`
UI setting.
- `Call` and `Network` panels now display additional time information.
#### Breaking
-
[expect(locator).toBeEditable()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-be-editable )
and
[locator.isEditable()](https://playwright.dev/docs/api/class-locator#locator-is-editable )
now throw if the target element is not `<input>`, `<select>`, or a
number of other editable elements.
- Option
[testConfig.updateSnapshots](https://playwright.dev/docs/api/class-testconfig#test-config-update-snapshots )
now updates all snapshots when set to `all`, rather than only the
failed/changed snapshots. Use the new enum `changed` to keep the old
functionality of only updating the changed snapshots.
#### Browser Versions
- Chromium 133.0.6943.16
- Mozilla Firefox 134.0
- WebKit 18.2
This version was also tested against the following stable channels:
- Google Chrome 132
- Microsoft Edge 132
###
[`v1.49.1`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.49.1 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.49.0...v1.49.1 )
##### Highlights
[https://github.com/microsoft/playwright/issues/33802 ](https://redirect.github.com/microsoft/playwright/issues/33802 )
- \[Bug]: Codegen's Clear button doesn't work if not
recording[https://github.com/microsoft/playwright/issues/33806 ](https://redirect.github.com/microsoft/playwright/issues/33806 )6
- \[Bug]: playwright hangs while waiting for pending
navigation[https://github.com/microsoft/playwright/issues/33787 ](https://redirect.github.com/microsoft/playwright/issues/33787 )87
- \[Bug]: VSC extension isn't capturing all entered
te[https://github.com/microsoft/playwright/issues/33788 ](https://redirect.github.com/microsoft/playwright/issues/33788 )788
- \[Regression]: Double clicking the steps in trace viewer doesn't
filter
acti[https://github.com/microsoft/playwright/issues/33772 ](https://redirect.github.com/microsoft/playwright/issues/33772 )3772
- \[Bug]: aria_snapshot generates invalid yaml when combined with an
aria-label
attr[https://github.com/microsoft/playwright/issues/33791 ](https://redirect.github.com/microsoft/playwright/issues/33791 )33791
- \[Bug]: text input with number value raises "container is not
iterable" with
to_match_aria_sna[https://github.com/microsoft/playwright/issues/33644 ](https://redirect.github.com/microsoft/playwright/issues/33644 )/33644
- \[Bug]: getByRole can't find element with the accessible name from
label element when aria-labelledby is
not[https://github.com/microsoft/playwright/issues/33660 ](https://redirect.github.com/microsoft/playwright/issues/33660 )s/33660
- \[Regression]: Unable to open Playwright UI in Dark Mode
#### Browser Versions
- Chromium 131.0.6778.33
- Mozilla Firefox 132.0
- WebKit 18.2
This version was also tested against the following stable channels:
- Google Chrome 130
- Microsoft Edge 130
###
[`v1.49.0`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.49.0 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.48.2...v1.49.0 )
#### Aria snapshots
New assertion
[expect(locator).toMatchAriaSnapshot()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-match-aria-snapshot )
verifies page structure by comparing to an expected accessibility tree,
represented as YAML.
```js
await page.goto('https://playwright.dev ');
await expect(page.locator('body')).toMatchAriaSnapshot(`
- banner:
- heading /Playwright enables reliable/ [level=1]
- link "Get started"
- link "Star microsoft/playwright on GitHub"
- main:
- img "Browsers (Chromium, Firefox, WebKit)"
- heading "Any browser • Any platform • One API"
`);
```
You can generate this assertion with [Test
Generator](https://playwright.dev/docs/codegen ) and update the expected
snapshot with `--update-snapshots` command line flag.
Learn more in the [aria snapshots
guide](https://playwright.dev/docs/aria-snapshots ).
#### Test runner
- New option
[testConfig.tsconfig](https://playwright.dev/docs/api/class-testconfig#test-config-tsconfig )
allows to specify a single `tsconfig` to be used for all tests.
- New method
[test.fail.only()](https://playwright.dev/docs/api/class-test#test-fail-only )
to focus on a failing test.
- Options
[testConfig.globalSetup](https://playwright.dev/docs/api/class-testconfig#test-config-global-setup )
and
[testConfig.globalTeardown](https://playwright.dev/docs/api/class-testconfig#test-config-global-teardown )
now support multiple setups/teardowns.
- New value `'on-first-failure'` for
[testOptions.screenshot](https://playwright.dev/docs/api/class-testoptions#test-options-screenshot ).
- Added "previous" and "next" buttons to the HTML report to quickly
switch between test cases.
- New properties
[testInfoError.cause](https://playwright.dev/docs/api/class-testinfoerror#test-info-error-cause )
and
[testError.cause](https://playwright.dev/docs/api/class-testerror#test-error-cause )
mirroring
[`Error.cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause ).
#### Breaking: channels `chrome`, `msedge` and similar switch to new
headless
This change affects you if you're using one of the following channels in
your `playwright.config.ts`:
- `chrome`, `chrome-dev`, `chrome-beta`, or `chrome-canary`
- `msedge`, `msedge-dev`, `msedge-beta`, or `msedge-canary`
##### What do I need to do?
After updating to Playwright v1.49, run your test suite. If it still
passes, you're good to go. If not, you will probably need to update your
snapshots, and adapt some of your test code around PDF viewers and
extensions. See [issue
#​33566](https://redirect.github.com/microsoft/playwright/issues/33566 )
for more details.
#### Other breaking changes
- There will be no more updates for WebKit on Ubuntu 20.04 and Debian
11. We recommend updating your OS to a later version.
- Package `@playwright/experimental-ct-vue2` will no longer be updated.
- Package `@playwright/experimental-ct-solid` will no longer be updated.
#### Try new Chromium headless
You can opt into the new headless mode by using `'chromium'` channel. As
[official Chrome documentation puts
it](https://developer.chrome.com/blog/chrome-headless-shell ):
> New Headless on the other hand is the real Chrome browser, and is thus
more authentic, reliable, and offers more features. This makes it more
suitable for high-accuracy end-to-end web app testing or browser
extension testing.
See [issue
#​33566](https://redirect.github.com/microsoft/playwright/issues/33566 )
for the list of possible breakages you could encounter and more details
on Chromium headless. Please file an issue if you see any problems after
opting in.
```js
import { defineConfig, devices } from '@​playwright/test';
export default defineConfig({
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'], channel: 'chromium' },
},
],
});
```
#### Miscellaneous
- `<canvas>` elements inside a snapshot now draw a preview.
- New method
[tracing.group()](https://playwright.dev/docs/api/class-tracing#tracing-group )
to visually group actions in the trace.
- Playwright docker images switched from Node.js v20 to Node.js v22 LTS.
#### Browser Versions
- Chromium 131.0.6778.33
- Mozilla Firefox 132.0
- WebKit 18.2
This version was also tested against the following stable channels:
- Google Chrome 130
- Microsoft Edge 130
###
[`v1.48.2`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.48.2 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.48.1...v1.48.2 )
##### Highlights
[https://github.com/microsoft/playwright/issues/33141 ](https://redirect.github.com/microsoft/playwright/issues/33141 )
- \[Bug]: UI Mode
crashed[https://github.com/microsoft/playwright/issues/33219 ](https://redirect.github.com/microsoft/playwright/issues/33219 )9
- \[BUG] Trace Viewer PWA crashes with "Aw,
Snap86
- \[Bug]: UI Mode Memory
probl[https://github.com/microsoft/playwright/issues/33000 ](https://redirect.github.com/microsoft/playwright/issues/33000 )000
- \[Regression]: Inspector and Browser doesn't close on
CTR[https://github.com/microsoft/playwright/issues/33204 ](https://redirect.github.com/microsoft/playwright/issues/33204 )3204
- \[Bug]: Chrome tab and inspector not closing after terminating session
in terminal
#### Browser Versions
- Chromium 130.0.6723.19
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 129
- Microsoft Edge 129
###
[`v1.48.1`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.48.1 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.48.0...v1.48.1 )
##### Highlights
[https://github.com/microsoft/playwright/issues/33023 ](https://redirect.github.com/microsoft/playwright/issues/33023 )
- \[Bug]: command line flag --headed has no effect in ui
mode[https://github.com/microsoft/playwright/issues/33107 ](https://redirect.github.com/microsoft/playwright/issues/33107 )7
- \[REGRESSION]: page.waitForRequest does not get resolved since
1.48.[https://github.com/microsoft/playwright/issues/33085 ](https://redirect.github.com/microsoft/playwright/issues/33085 )85
- \[Bug]: WebSocket route does not handle full URLs in
Playwrig[https://github.com/microsoft/playwright/issues/33052 ](https://redirect.github.com/microsoft/playwright/issues/33052 )052
- \[Regression]: Inspector not showing recorded
st[https://github.com/microsoft/playwright/issues/33132 ](https://redirect.github.com/microsoft/playwright/issues/33132 )3132
- \[Bug]: Wrong Ubuntu release name in
Dockerfile.n[https://github.com/microsoft/playwright/pull/32996 ](https://redirect.github.com/microsoft/playwright/pull/32996 )32996
- \[BUG] Trace attachments have small unusable height
#### Browser Versions
- Chromium 130.0.6723.19
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 129
- Microsoft Edge 129
###
[`v1.48.0`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.48.0 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.47.2...v1.48.0 )
#### WebSocket routing
New methods
[page.routeWebSocket()](https://playwright.dev/docs/api/class-page#page-route-web-socket )
and
[browserContext.routeWebSocket()](https://playwright.dev/docs/api/class-browsercontext#browser-context-route-web-socket )
allow to intercept, modify and mock WebSocket connections initiated in
the page. Below is a simple example that mocks WebSocket communication
by responding to a `"request"` with a `"response"`.
```js
await page.routeWebSocket('/ws', ws => {
ws.onMessage(message => {
if (message === 'request')
ws.send('response');
});
});
```
See
[WebSocketRoute](https://playwright.dev/docs/api/class-websocketroute )
for more details.
#### UI updates
- New "copy" buttons for annotations and test location in the HTML
report.
- Route method calls like
[route.fulfill()](https://playwright.dev/docs/api/class-route#route-fulfill )
are not shown in the report and trace viewer anymore. You can see which
network requests were routed in the network tab instead.
- New "Copy as cURL" and "Copy as fetch" buttons for requests in the
network tab.
#### Miscellaneous
- Option
[`form`](https://playwright.dev/docs/api/class-apirequestcontext#api-request-context-fetch-option-form )
and similar ones now accept
[FormData](https://playwright.dev/docs/api/class-formdata ).
- New method
[page.requestGC()](https://playwright.dev/docs/api/class-page#page-request-gc )
may help detect memory leaks.
- New option
[`location`](https://playwright.dev/docs/api/class-test#test-step-option-location )
to pass custom step location.
- Requests made by
[APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext )
now record detailed timing and security information in the HAR.
#### Browser Versions
- Chromium 130.0.6723.19
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 129
- Microsoft Edge 129
###
[`v1.47.2`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.47.2 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.47.1...v1.47.2 )
##### Highlights
[https://github.com/microsoft/playwright/pull/32699 ](https://redirect.github.com/microsoft/playwright/pull/32699 )-
\[REGRESSION]: fix(codegen): use content_frame property in
python/.NET[https://github.com/microsoft/playwright/issues/32706 ](https://redirect.github.com/microsoft/playwright/issues/32706 )6-
\[REGRESSION]: page.pause() does not pause test timeout after
1.4[https://github.com/microsoft/playwright/pull/32661 ](https://redirect.github.com/microsoft/playwright/pull/32661 )61
- fix(trace-viewer): time delta between local and remote actions
#### Browser Versions
- Chromium 129.0.6668.29
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 128
- Microsoft Edge 128
###
[`v1.47.1`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.47.1 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.47.0...v1.47.1 )
##### Highlights
[https://github.com/microsoft/playwright/issues/32480 ](https://redirect.github.com/microsoft/playwright/issues/32480 )
- \[REGRESSION]: tsconfig.json's compilerOptions.paths no longer working
in
1.47[https://github.com/microsoft/playwright/issues/32552 ](https://redirect.github.com/microsoft/playwright/issues/32552 )2
- \[REGRESSION]: broken UI in Trace Viewer while showing network
response body
#### Browser Versions
- Chromium 129.0.6668.29
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 128
- Microsoft Edge 128
###
[`v1.47.0`](https://redirect.github.com/microsoft/playwright/releases/tag/v1.47.0 )
[Compare
Source](https://redirect.github.com/microsoft/playwright/compare/v1.46.1...v1.47.0 )
#### Network Tab improvements
The Network tab in the UI mode and trace viewer has several nice
improvements:
- filtering by asset type and URL
- better display of query string parameters
- preview of font assets

Credit to [@​kubajanik](https://redirect.github.com/kubajanik ) for
these wonderful improvements!
#### `--tsconfig` CLI option
By default, Playwright will look up the closest tsconfig for each
imported file using a heuristic. You can now specify a single tsconfig
file in the command line, and Playwright will use it for all imported
files, not only test files:
```sh
### Pass a specific tsconfig
npx playwright test --tsconfig tsconfig.test.json
```
####
[APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext )
now accepts
[`URLSearchParams`](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams )
and `string` as query parameters
You can now pass
[`URLSearchParams`](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams )
and `string` as query parameters to
[APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext ):
```ts
test('query params', async ({ request }) => {
const searchParams = new URLSearchParams();
searchParams.set('userId', 1);
const response = await request.get(
'https://jsonplaceholder.typicode.com/posts ',
{
params: searchParams // or as a string: 'userId=1'
}
);
// ...
});
```
#### Miscellaneous
- The `mcr.microsoft.com/playwright:v1.47.0` now serves a Playwright
image based on Ubuntu 24.04 Noble.
To use the 22.04 jammy-based image, please use
`mcr.microsoft.com/playwright:v1.47.0-jammy` instead.
- The `:latest`/`:focal`/`:jammy` tag for Playwright Docker images is no
longer being published. Pin to a specific version for better stability
and reproducibility.
- New option `behavior` in
[page.removeAllListeners()](https://playwright.dev/docs/api/class-page#page-remove-all-listeners ),
[browser.removeAllListeners()](https://playwright.dev/docs/api/class-browser#browser-remove-all-listeners )
and
[browserContext.removeAllListeners()](https://playwright.dev/docs/api/class-browsercontext#browser-context-remove-all-listeners )
to wait for ongoing listeners to complete.
- TLS client certificates can now be passed from memory by passing
`cert` and `key` as buffers instead of file paths.
- Attachments with a `text/html` content type can now be opened in a new
tab in the HTML report. This is useful for including third-party reports
or other HTML content in the Playwright test report and distributing it
to your team.
- `noWaitAfter` in
[locator.selectOption()](https://playwright.dev/docs/api/class-locator#locator-select-option )
was deprecated.
- We've seen reports of WebGL in Webkit misbehaving on GitHub Actions
`macos-13`. We recommend upgrading GitHub Actions to `macos-14`.
#### Browser Versions
- Chromium 129.0.6668.29
- Mozilla Firefox 130.0
- WebKit 18.0
This version was also tested against the following stable channels:
- Google Chrome 128
- Microsoft Edge 128
</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://redirect.github.com/renovatebot/renovate/discussions ) if
that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/ ).
View the [repository job
log](https://developer.mend.io/github/ionic-team/ionic-framework ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC41OS4yIiwidXBkYXRlZEluVmVyIjoiMzkuMjAwLjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: ionitron <hi@ionicframework.com>
2025-03-14 16:54:45 +00:00
1e757513ce
feat(ionic-theme): improve scss architecture for ionic theme ( #29345 )
...
Issue number: None
---------
<!-- 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 new behavior?
<!-- Please describe the behavior or changes that are being added by
this PR. -->
This PR follows the architectural changes defined on the _SCSS
Architecture Design Doc_. Due to some of the developments done in the
meantime, not everything that was defined on that document was followed
and some sections were simplified.
Overall, there were two guidelines that supported the work on this PR:
- Have no impact on the current scss partials & CSS architecture for the
`md/iOS` themes.
- Make everything related to the new `Ionic` Theme separated.
Based on these, here're the changes made:
**On Themes folder (private):**
- Renamed current internal scss partials on src/themes, related to
md/iOS, to `native.*.scss` and move them to a new folder, called
`native`. Updated imports on all framework.
- Removed the ionic prefix from the name of the mixins and function
partials on src/themes. Updated imports on all framework.
- Created new folder, named ionic, inside src/themes. This holds the
`ionic.globals.scss`, with all the mixins and functions forwarded, to be
used on other scopes.
- Replaced on already created Ionic theme files, the usage of tokens and
mixins with @use, to instead _@use
"../../themes/ionic/ionic.globals.scss" as globals;_. This ensures an
equal approach is followed everywhere and also makes it easier to change
the files imported or paths, in the future, as its all in the same
global file.
- Updated the foundations `readMe` file, with the new process for using
globals.

**On css folder (public):**
- Created new folder, named `ionic`, inside src/css. This holds all the
files related exclusively to Ionic Theme, following the same structure
as exists now for md/iOS, with a core, a bundle, utils, etc. Some files
were a bit duplicated, to eliminate imports from ios or md theme
partials. The only file common to both Themes is the `normalize.scss`.
- No folder structure or renamings were done on the existing output, to
prevent breaking-changes for developers already making imports from this
folder.
- Updated typography and link partials to use globals instead of tokens.
- Changed `font-size` styles on typography to be on `body`, instead of
`html`, to enable correct support of accessibility features on browsers
and devices, related to `font-size`.

**Other changes related to global styles new architecture:**
- Updated margin & padding utility-classed generated by token, to
include css variables and padding/margin mixins.
- Updated link test to use new global Ionic bundle, correct
utility-class on ion-content and updated snapshots. The font-size
changed to 16, as its now the default on the body.
- Updated typography snapshots.
- Updated prettier format on all scss files. Later on we should make
sure this is equal for all team members.
## 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.
-->
---------
Co-authored-by: Sean Perkins <sean@ionic.io>
2024-04-18 17:22:24 +01:00
284eb8ecaf
feat: add ionic theme architecture ( #29132 )
...
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. -->
## What is the new behavior?
<!-- Please describe the behavior or changes that are being added by
this PR. -->
Adds the base architecture to add a new theme configuration to Ionic
Framework components.
- Components can now specify an additional stylesheet for the `ionic`
theme.
- Developers can specify the `theme` and `mode` independently to control
look and feel of a component.
Test infrastructure has been updated to add support for testing the
theme configuration with Playwright.
- Existing `themes` test configuration has been renamed to `palettes`
This PR is just the initial effort to decouple Ionic's architecture to
separate look and feel and allow our dev team to start introducing the
new component appearance to the UI. There will be additional changes
required to completely add support for the Ionic theme. These changes
are targeted against the `next` branch and are not expected to be used
in a production environment at this time.
## 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: Maria Hutt <thetaPC@users.noreply.github.com>
Co-authored-by: Brandy Carney <brandyscarney@users.noreply.github.com>
2024-03-18 15:45:01 -04:00
82b607d6e3
test(thumbnail): migrate to generators ( #27381 )
...
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. -->
Thumbnail tests are using legacy syntax
## What is the new behavior?
<!-- Please describe the behavior or changes that are being added by
this PR. -->
- Thumbnail tests are using modern syntax
## 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. -->
2023-05-04 00:06:41 +00:00
4826a3d9f5
test(config): introduce legacy and modern playwright projects ( #27228 )
...
Issue number: N/A
---------
<!-- Please refer to our contributing documentation for any questions on
submitting a pull request, or let us know here if you need any help:
https://ionicframework.com/docs/building/contributing -->
<!-- Some docs updates need to be made in the `ionic-docs` repo, in a
separate PR. See
https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#modifying-documentation
for details. -->
<!-- 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. -->
This is the first PR to introduce the infrastructure required to add
test generators to the Ionic Framework project. This PR introduces the
file name changes necessary to support two playwright configs, so I
recommend reviewing the PR by commit:
1e5012cea1
- Created a `playwright.config-legacy.ts` file and updates
`package.json`.
- Running `npm run test.e2e` will run the generator tests, and running
`npm run test.e2e.legacy` will run the legacy tests.
4fe8de7df7
- Updates the GitHub Action scripts to run both the modern and legacy
E2E tests. I added command modifiers to avoid collisions with output
directories.
e8bcfaf926
- Updates `*.e2e.ts` files to have the legacy format name:
`*.e2e-legacy.ts`. This naming scheme is required for the two Playwright
configs to pull in the correct files. When migrating tests to
generators, team members will rename the file to remove the `-legacy`
part.
5bf196c36d
(warning: lots of files!)
- Updates the `*.e2e.ts-snapshots` directories to have the legacy format
name: `*.e2e-legacy.ts-snapshots`. The screenshot directory in
Playwright is generated based on the test file name which is why we are
updating the screenshot directory. When migrating tests to generators,
team members will rename the directory to remove the `-legacy` part.
## 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. -->
2023-04-26 18:27:17 +00:00
8ff83b8098
chore(): add updated snapshots
2023-03-29 13:40:26 +00:00
f750c8756f
chore(): sync with main
2023-03-29 09:17:21 -04:00
6cecdf4145
fix(item): use thumbnail's size when present ( #27014 )
...
resolves #22935
---------
Co-authored-by: ionitron <hi@ionicframework.com>
Co-authored-by: liamdebeasi <liamdebeasi@users.noreply.github.com>
2023-03-24 11:32:14 -07:00
c3b619f76f
chore(): add updated snapshots
2023-02-22 15:40:01 +00:00
799871e95d
chore(): sync with main
2023-02-22 10:00:56 -05:00
804e54e5ca
test(many): migrate to new toHaveScreenshot API ( #26797 )
2023-02-16 11:37:29 -05:00
b78b454e08
revert(): revert base components feature ( #26692 )
...
The Ionic Framework team would like to re-evaluate our approach to improving customization options when building mobile applications. We are looking at other solutions that a) make customizing an app UI easier and b) are applicable to a broader set of developers.
2023-01-30 11:52:36 -05:00
18f109c7da
feat(base-components): add ability to remove ios and md theme ( #26669 )
2023-01-24 16:18:35 -05:00
96147ec1b0
fix(item): ios mode has correct padding ( #26511 )
2023-01-04 16:54:43 -05:00
eea91bbbe1
fix(item): align iOS font size to spec ( #26445 )
2022-12-08 16:24:02 -05:00
419b1cb461
test(thumbnail): migrate to playwright ( #26022 )
2022-09-27 12:20:56 -04:00
15c169043f
chore(docs): remove manual documentation ( #24984 )
2022-04-21 12:31:51 -04:00
5676bab316
lint(eslint): migrate to eslint and prettier ( #25046 )
2022-04-04 11:12:53 -04:00
a9b2260100
test(core): add lang attr to html tag to resolve axe errors ( #22410 )
2020-11-02 17:08:03 -05:00
db2cac20fb
docs(vue): update component usage examples for vue 3 ( #22050 )
2020-09-11 13:48:21 -04:00
687122127c
docs(stencil): add stencil usage to components ( #21261 )
2020-05-12 20:35:48 -04:00
da6263a044
docs(vue): update usage examples to kebab-case ( #20313 )
...
references #20296
2020-01-27 14:22:42 -05:00
930b271a4a
Master react ( #18998 )
...
* chore(): bump to beta 8
* fix(): IonFabButton href fix
* fix(react): support components with href attributes
* fix(): Prep work to break router out
* fix(): breaking react-router and react-core into own packages
* chore(): moving view stuff out of react-core
* chore(): dev build 8-1
* chore(): update to react beta 8
* chore(): fixes to deps
* fix(): removing IonAnchor in favor of IonRouterLink
* chore(): beta 9 release
* refactor(react): treeshake, minify, api
* wip
* fix(): react dev builds
* fix(): fixes to get app builds working again
* fix(): removing tgz file
* feat(): adding platform helper methods
* fix(): don't map attributes to props
* chore(): add test app
* feat(): copy css folder from core
* chore(): move rollup node resolve to devDependencies
* fix(): expose setupConfig()
* perf(): improve treeshaking
* fix(): removing crypto from generateUniqueId
* fix(): adding missing rollup dp
* fix(): test cleanup and fixes to make tests pass
* chore(): moving react to packages folder
* fix(): fixing react build due to move to packages
* feat(): adding missing IonInfiniteScrollContent component
* chore(): add automated testing using cypress
* fix(): adding option onDidDismiss to controller components
* 0.0.10 react
* wip
* fix(): removing deprecated React calls
* fix(): exporting setupConfig from core
* chore(): bump to 4.8.0-rc.0
* chore(): updating test-app deps and fixing test
* chore(): updates to react readme
2019-08-13 14:24:44 -06:00
e82648bda2
refactor(all): update to one (part 3) ( #18874 )
2019-07-25 20:22:44 +02:00
598a13ecc0
chore(test): remove unused preview tests ( #18608 )
2019-06-24 17:15:57 -05:00
34dfc3ce98
refactor(all): updating to newest stencil apis ( #18578 )
...
* chore(): update ionicons
* refactor(all): updating to newest stencil apis
* fix lint issues
* more changes
* moreee
* fix treeshaking
* fix config
* fix checkbox
* fix stuff
* chore(): update ionicons
* fix linting errors
2019-06-23 11:26:42 +02:00
b40f7d36d5
fix(): update to Stencil One 🎉 🎊
2019-06-19 21:33:50 +02:00
fbb76e63ad
test(): remove external images ( #18413 )
...
* chore(test): replace img in favor of datauri
* remove external images
2019-05-29 15:01:46 -04:00
e5c8c10029
fix(components): include mode classes on components for use in shadow ( #17838 )
...
- removes mode-less component classes from the internal CSS, use element instead
- adds mode specific classes `md` or `ios` for styling inside of shadow components
- adds e2e test that verifies mode classes exist on all ionic components, plus checks for specific classes that the components need for internal styling
fixes #17608
2019-04-16 17:28:21 -04:00
22d1aeebaa
docs(react): update component usage docs ( #17615 )
2019-02-26 08:54:01 -06:00
c68292b78f
test(rtl): add rtl script to all e2e tests ( #17009 )
2019-01-08 15:06:23 -06:00
7ba94900bb
refactor(themes): remove the outer-content class from core ( #16589 )
...
BREAKING CHANGES
The outer-content class has been removed in favor of setting the color in your app instead:
```
.outer-content {
--background: #f2f2f2;
}
```
2018-12-04 16:38:50 -05:00
6b7f8ae201
chore(): update stencil ( #16506 )
2018-11-29 18:54:51 +01:00
018fb9876f
test(all): use test() instead of it() where appropriate ( #16129 )
...
This replaces uses of Jest's it() function in end-to-end tests with the alias test() where it makes sense semantically.
2018-10-29 12:40:06 -05:00
3c7fee5cca
test(e2e): relative paths ( #16077 )
2018-10-24 22:41:48 -05:00
a9fd3399de
test(e2e): force roboto font on all systems ( #15993 )
2018-10-19 15:22:15 -05:00
07d135bcfc
test(thumbnail): use SVG thumbnail image
2018-10-12 11:08:17 -05:00
ae3271f2d7
test(all): inject test styles on flag
2018-10-11 15:13:23 -05:00
2172aa9dae
test(screenshot): use Arial for testing
2018-10-09 13:40:31 -05:00
f2d16a58fa
test(thumbnail): migrate e2e tests
...
references #15803
2018-10-01 13:56:32 -05:00
c49d896e08
refactor(all): using ComponentInterface
2018-09-14 18:47:00 +02:00
096d9a76f3
fix(css): add core.css ( #15220 )
...
fixes #15170
2018-08-29 18:05:20 +02:00
771857b1df
refactor(thumbnail): make it mode less
2018-08-26 01:35:42 +02:00
c88e1adfd8
fix(thumbnail): add and document custom properties
...
references #14850
2018-08-08 14:31:33 -05:00
c1b61d0fee
chore(): update to ionic-rules/strict
2018-07-29 23:10:38 +02:00
2c37a5a7b2
docs(previews): update preview tests to have translucent white toolbars
...
to make ben happy
2018-07-24 16:27:17 -04:00
094fde755c
style(css): fix most scss lint errors
2018-07-18 12:53:33 -04:00
a7f1f4daa7
refactor(components): update to use shadow DOM and work with css variables
...
- updates components to use shadow DOM or scoped if they require css variables
- moves global styles to an external stylesheet that needs to be imported
- adds support for additional colors and removes the Sass loops to generate colors for each component
- several property renames, bug fixes, and test updates
Co-authored-by: Manu Mtz.-Almeida <manu.mtza@gmail.com>
Co-authored-by: Adam Bradley <adambradley25@gmail.com>
Co-authored-by: Cam Wiegert <cam@camwiegert.com>
2018-07-09 12:57:21 -04:00
96945b1ee1
docs(): usage and examples
2018-06-18 12:45:15 -04:00