fix(datetime): ensure datetime is shown when intersection observer fails to report visibility #17461
build.yml
on: pull_request
build-core
1m 8s
Matrix: test-core-screenshot
test-core-clean-build
15s
test-core-lint
49s
test-core-spec
41s
verify-screenshots
4s
Matrix: test-angular-e2e
Matrix: test-react-e2e
Matrix: test-react-router-e2e
Matrix: test-vue-e2e
verify-test-angular-e2e
2s
verify-test-react-e2e
2s
verify-test-react-router-e2e
3s
verify-test-vue-e2e
3s
Annotations
34 errors and 16 notices
|
[Mobile Chrome] › src/components/radio/test/a11y/radio.e2e.ts:117:11 › radio: a11y - md/ltr › radio: keyboard navigation - md/ltr › tabbing should switch between radio groups:
src/components/radio/test/a11y/radio.e2e.ts#L122
1) [Mobile Chrome] › src/components/radio/test/a11y/radio.e2e.ts:117:11 › radio: a11y - md/ltr › radio: keyboard navigation - md/ltr › tabbing should switch between radio groups
Error: expect(locator).toBeFocused() failed
Locator: locator('#first-group ion-radio').first()
Expected: focused
Received: inactive
Timeout: 5000ms
Call log:
- Expect "toBeFocused" with timeout 5000ms
- waiting for locator('#first-group ion-radio').first()
9 × locator resolved to <ion-radio value="huey" role="radio" tabindex="0" aria-checked="true" class="md in-item radio-checked radio-label-placement-start hydrated">Huey</ion-radio>
- unexpected value "inactive"
120 |
121 | await pageUtils.pressKeys('Tab');
> 122 | await expect(firstGroupRadios.nth(0)).toBeFocused();
| ^
123 |
124 | await pageUtils.pressKeys('Tab');
125 | await expect(secondGroupRadios.nth(0)).toBeFocused();
at /ionic/src/components/radio/test/a11y/radio.e2e.ts:122:47
|
|
test-core-screenshot (9, 20)
Process completed with exit code 1.
|
|
[Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L203
1) [Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 30000ms exceeded.
Call log:
- waiting for locator('ion-datetime').locator('.calendar-day:not([disabled])').first()
- locator resolved to <button data-day="1" tabindex="-1" data-index="3" data-month="10" data-year="2025" part="calendar-day" data-day-of-week="3" class="calendar-day" aria-label="Wednesday, October 1">1</button>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 100ms
56 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 500ms
201 |
202 | const firstEnabledDay = datetime.locator('.calendar-day:not([disabled])').first();
> 203 | await firstEnabledDay.click();
| ^
204 | await page.waitForChanges();
205 |
206 | await openAndInteract();
at /ionic/src/components/datetime-button/test/overlays/datetime-button.e2e.ts:203:29
|
|
[Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L0
1) [Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 30000ms exceeded.
|
|
[Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L203
1) [Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 30000ms exceeded.
Call log:
- waiting for locator('ion-datetime').locator('.calendar-day:not([disabled])').first()
- locator resolved to <button data-day="1" tabindex="-1" data-index="3" data-month="10" data-year="2025" part="calendar-day" data-day-of-week="3" class="calendar-day" aria-label="Wednesday, October 1">1</button>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 100ms
56 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 500ms
201 |
202 | const firstEnabledDay = datetime.locator('.calendar-day:not([disabled])').first();
> 203 | await firstEnabledDay.click();
| ^
204 | await page.waitForChanges();
205 |
206 | await openAndInteract();
at /ionic/src/components/datetime-button/test/overlays/datetime-button.e2e.ts:203:29
|
|
[Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L0
1) [Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 30000ms exceeded.
|
|
[Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L203
1) [Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Error: locator.click: Test timeout of 30000ms exceeded.
Call log:
- waiting for locator('ion-datetime').locator('.calendar-day:not([disabled])').first()
- locator resolved to <button data-day="1" tabindex="-1" data-index="3" data-month="10" data-year="2025" part="calendar-day" data-day-of-week="3" class="calendar-day" aria-label="Wednesday, October 1">1</button>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 100ms
56 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 500ms
201 |
202 | const firstEnabledDay = datetime.locator('.calendar-day:not([disabled])').first();
> 203 | await firstEnabledDay.click();
| ^
204 | await page.waitForChanges();
205 |
206 | await openAndInteract();
at /ionic/src/components/datetime-button/test/overlays/datetime-button.e2e.ts:203:29
|
|
[Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L0
1) [Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Test timeout of 30000ms exceeded.
|
|
test-core-screenshot (1, 20)
The strategy configuration was canceled because "test-core-screenshot._9_20" failed
|
|
test-core-screenshot (1, 20)
Process completed with exit code 12.
|
|
test-core-screenshot (1, 20)
The operation was canceled.
|
|
test-core-screenshot (2, 20)
The strategy configuration was canceled because "test-core-screenshot._9_20" failed
|
|
test-core-screenshot (2, 20)
Process completed with exit code 12.
|
|
test-core-screenshot (2, 20)
The operation was canceled.
|
|
test-core-screenshot (3, 20)
The strategy configuration was canceled because "test-core-screenshot._9_20" failed
|
|
test-core-screenshot (3, 20)
Process completed with exit code 12.
|
|
test-core-screenshot (3, 20)
The operation was canceled.
|
|
test-core-screenshot (16, 20)
Process completed with exit code 1.
|
|
[Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L203
1) [Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 30000ms exceeded.
Call log:
- waiting for locator('ion-datetime').locator('.calendar-day:not([disabled])').first()
- locator resolved to <button data-day="1" tabindex="-1" data-index="3" data-month="10" data-year="2025" part="calendar-day" data-day-of-week="3" class="calendar-day" aria-label="Wednesday, October 1">1</button>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 100ms
53 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 500ms
201 |
202 | const firstEnabledDay = datetime.locator('.calendar-day:not([disabled])').first();
> 203 | await firstEnabledDay.click();
| ^
204 | await page.waitForChanges();
205 |
206 | await openAndInteract();
at /ionic/src/components/datetime-button/test/overlays/datetime-button.e2e.ts:203:29
|
|
[Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L0
1) [Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 30000ms exceeded.
|
|
[Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L203
1) [Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Test timeout of 30000ms exceeded.
Call log:
- waiting for locator('ion-datetime').locator('.calendar-day:not([disabled])').first()
- locator resolved to <button data-day="1" tabindex="-1" data-index="3" data-month="10" data-year="2025" part="calendar-day" data-day-of-week="3" class="calendar-day" aria-label="Wednesday, October 1">1</button>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 100ms
53 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 500ms
201 |
202 | const firstEnabledDay = datetime.locator('.calendar-day:not([disabled])').first();
> 203 | await firstEnabledDay.click();
| ^
204 | await page.waitForChanges();
205 |
206 | await openAndInteract();
at /ionic/src/components/datetime-button/test/overlays/datetime-button.e2e.ts:203:29
|
|
[Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L0
1) [Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 30000ms exceeded.
|
|
[Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L203
1) [Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Error: locator.click: Test timeout of 30000ms exceeded.
Call log:
- waiting for locator('ion-datetime').locator('.calendar-day:not([disabled])').first()
- locator resolved to <button data-day="1" tabindex="-1" data-index="3" data-month="10" data-year="2025" part="calendar-day" data-day-of-week="3" class="calendar-day" aria-label="Wednesday, October 1">1</button>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 100ms
53 × waiting for element to be visible, enabled and stable
- element is not visible
- retrying click action
- waiting 500ms
- waiting for element to be visible, enabled and stable
201 |
202 | const firstEnabledDay = datetime.locator('.calendar-day:not([disabled])').first();
> 203 | await firstEnabledDay.click();
| ^
204 | await page.waitForChanges();
205 |
206 | await openAndInteract();
at /ionic/src/components/datetime-button/test/overlays/datetime-button.e2e.ts:203:29
|
|
[Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal:
src/components/datetime-button/test/overlays/datetime-button.e2e.ts#L0
1) [Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
Test timeout of 30000ms exceeded.
|
|
test-core-screenshot (4, 20)
The strategy configuration was canceled because "test-core-screenshot._9_20" failed
|
|
test-core-screenshot (4, 20)
Process completed with exit code 12.
|
|
test-core-screenshot (4, 20)
The operation was canceled.
|
|
test-core-screenshot (6, 20)
The strategy configuration was canceled because "test-core-screenshot._9_20" failed
|
|
test-core-screenshot (6, 20)
The operation was canceled.
|
|
test-core-screenshot (5, 20)
The strategy configuration was canceled because "test-core-screenshot._9_20" failed
|
|
test-core-screenshot (5, 20)
The operation was canceled.
|
|
test-core-screenshot (15, 20)
The strategy configuration was canceled because "test-core-screenshot._9_20" failed
|
|
verify-screenshots
Process completed with exit code 1.
|
|
Ionic Framework Build
Canceling since a higher priority waiting request for refs/pull/30793/merge exists
|
|
🎭 Playwright Run Summary
216 skipped
257 passed (2.3m)
|
|
🎭 Playwright Run Summary
534 passed (3.1m)
|
|
🎭 Playwright Run Summary
1 skipped
537 passed (3.3m)
|
|
🎭 Playwright Run Summary
1 skipped
534 passed (3.2m)
|
|
🎭 Playwright Run Summary
212 skipped
313 passed (3.6m)
|
|
🎭 Playwright Run Summary
1 flaky
[Mobile Chrome] › src/components/radio/test/a11y/radio.e2e.ts:117:11 › radio: a11y - md/ltr › radio: keyboard navigation - md/ltr › tabbing should switch between radio groups
4 skipped
514 passed (3.8m)
|
|
🎭 Playwright Run Summary
648 passed (4.3m)
|
|
🎭 Playwright Run Summary
10 skipped
503 passed (4.9m)
|
|
🎭 Playwright Run Summary
1 failed
[Mobile Chrome] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
4 skipped
510 passed (4.9m)
|
|
🎭 Playwright Run Summary
14 skipped
399 passed (5.0m)
|
|
🎭 Playwright Run Summary
1 failed
[Mobile Safari] › src/components/datetime-button/test/overlays/datetime-button.e2e.ts:179:9 › datetime-button: modal - md/ltr › should set datetime ready state and keep calendar interactive when reopening modal
5 skipped
512 passed (6.7m)
|
|
🎭 Playwright Run Summary
5 skipped
517 passed (7.0m)
|
|
🎭 Playwright Run Summary
5 skipped
573 passed (6.8m)
|
|
🎭 Playwright Run Summary
1 skipped
523 passed (6.8m)
|
|
🎭 Playwright Run Summary
10 skipped
529 passed (6.8m)
|
|
🎭 Playwright Run Summary
2 skipped
517 passed (7.1m)
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
ionic-angular
|
667 KB |
sha256:b197c732af424b4b507b4b415bff31e43addd013a2de5f0adbb3b66e921e868f
|
|
|
ionic-angular-server
|
8.55 KB |
sha256:c8f70b313220d21b40960c45fe6a5857503cda4f0964f639763ff569194cd61e
|
|
|
ionic-core
|
4.56 MB |
sha256:1766a9e3cfb2094c74a13499c004c206f163d24aa94d5b5e3085fcd5e0ac9698
|
|
|
ionic-react
|
211 KB |
sha256:d26ea6acc5cf5801c2bd2255f45aaf8c5ddd165d40820f1862175abeb097b1fd
|
|
|
ionic-react-router
|
27.9 KB |
sha256:5a6f81e503ee9ab931859e26b64b0714be9ac141038d8c05b09bbc4a68c8d957
|
|
|
ionic-vue
|
233 KB |
sha256:c7510a60be2de71e4085139dcc8f1d1f5e68850d58a4d1b31c1a1bf91cc1fee5
|
|
|
ionic-vue-router
|
17.1 KB |
sha256:531668a333161dab3d243e4bd4bde79eaa44afb0bae60515d275e9920635e62e
|
|
|
test-results-10-20
|
461 KB |
sha256:19df4cafdcb196582a7355347f78328f656b3f629a5a0bf44a418a60f7eb0dec
|
|
|
test-results-11-20
|
1.25 MB |
sha256:495b488498ecb8f3e4a24cb5466d01e96e7df715329f054e81d7bad0c8a0d3c2
|
|
|
test-results-12-20
|
442 KB |
sha256:5f3fc44c8832054a099ddfd885bc4600d809c0e39a105919f07edccf11e22f90
|
|
|
test-results-13-20
|
450 KB |
sha256:f8a8dd42c34559ed47375dfd3f1f421814c229fed24ddb3aa19d2dfb0c97e00a
|
|
|
test-results-14-20
|
405 KB |
sha256:1d666519a11d50d5eef0eec9b2cdf0c6d5ec62304cb2e7b0443f5d287d1f263e
|
|
|
test-results-15-20
|
431 KB |
sha256:682a3557979ec613970ee4b33570579032fac75b2eec1b3defd078f35d7e153c
|
|
|
test-results-16-20
|
2.33 MB |
sha256:19f7309dfc86d8600e786d5235749c4efecd9f41419d1021d12b146e66090767
|
|
|
test-results-17-20
|
529 KB |
sha256:7d51d6c89c847c2265f6f4a716a9508aa31a9b0321400817b23a4f9ebc0a4c01
|
|
|
test-results-18-20
|
505 KB |
sha256:dfce70050e9dba0b197643bfa1d3713f0ae8dea5adf2ab46b3d24a142c7a21f1
|
|
|
test-results-19-20
|
396 KB |
sha256:5470084bfb3bffe5090ed040fda27f36a8f94a8d33862406484c39ec747df6c2
|
|
|
test-results-20-20
|
360 KB |
sha256:407c0edc13bec340b2cfe596c793f36b42fc21c169bdaffb206036738f866977
|
|
|
test-results-5-20
|
453 KB |
sha256:9168699bdfb0f67aeed87e3a2ffa464c06f4384a4ee80453ee75c6f0d848f7b8
|
|
|
test-results-6-20
|
446 KB |
sha256:fdb4149b095eafdbaa75304fa5adb2f699515da2ae796777c9afd9e0ee93c916
|
|
|
test-results-7-20
|
351 KB |
sha256:c7172ca9102be9fe745a4f45da14e86ce59566da23a984d422abc894c2ca2406
|
|
|
test-results-8-20
|
428 KB |
sha256:3d66ebf52d38a99d004712121fa8bd5ce7cc8c719385dcefd1de013678d30e22
|
|
|
test-results-9-20
|
2.48 MB |
sha256:efe7a05f00b6fb2cd41369ae67e0c52d18b8aee9d7af5d9168d0c301843c90fb
|
|