Closed
Bug 1790830
Opened 2 years ago
Closed 2 years ago
[wpt-sync] Sync PR 35897 - Add keypress Event Timing Test
Categories
(Testing :: web-platform-tests, task, P4)
Testing
web-platform-tests
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 35897 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/35897
Details from upstream follow.
Han Gao <hangaoy@google.com> wrote:
Add keypress Event Timing Test
Added a test file to cover the keypress event, and also added a handler
to test utils to send a key in response to having keypress event.Bug:1255095
Change-Id: I2a1cbf036c782973d52a651743f095af2fd8222c
Reviewed-on: https://chromium-review.googlesource.com/3891891
WPT-Export-Revision: 10cd58d9f5dd0a9be2596dccd54b231d6141a522
|
Assignee | |
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
|
|
Assignee | |
Updated•2 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
|
|
Assignee | |
Updated•2 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
|
|
Assignee | |
Comment 1•2 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=ccf529dcb4d24a389a63d3075470d00b308dad65
|
|
Assignee | |
Comment 2•2 years ago
|
||
CI Results
Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI
Total 42 tests and 1 subtests
Status Summary
Firefox
OK : 40
PASS : 28
FAIL : 12
TIMEOUT: 4
Chrome
OK : 40
PASS : 40
TIMEOUT: 4
Safari
OK : 42
FAIL : 42
Links
Details
New Tests That Don't Pass
- /event-timing/crossiframe.html [wpt.fyi]
- Event Timing: entries should only be observable by its own frame.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: entries should only be observable by its own frame.:
- /event-timing/disconnect-target.html [wpt.fyi]
- Event Timing: when target is disconnected, entry.target returns null.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: when target is disconnected, entry.target returns null.:
- /event-timing/event-retarget.html [wpt.fyi]
- Event Timing: target reports the last Event Target, i.e. nothing from shadow DOM.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: target reports the last Event Target, i.e. nothing from shadow DOM.:
- /event-timing/first-input-interactionid-click.html [wpt.fyi]
- The interactionId of the first input entry should match the same pointerdown entry of event timing when click.:
FAIL(Chrome:PASS, Safari:FAIL)
- The interactionId of the first input entry should match the same pointerdown entry of event timing when click.:
- /event-timing/first-input-interactionid-tap.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:OK)- The interactionId of the first input entry should match the same pointerdown entry of event timing when tap.:
TIMEOUT(Chrome:TIMEOUT, Safari:FAIL)
- The interactionId of the first input entry should match the same pointerdown entry of event timing when tap.:
- /event-timing/interactionid-click.html [wpt.fyi]
- Event Timing: compare event timing interactionId.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: compare event timing interactionId.:
- /event-timing/interactionid-press-key-as-input.html [wpt.fyi]
- Event Timing: compare event timing interactionId for key press as input.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: compare event timing interactionId for key press as input.:
- /event-timing/interactionid-press-key-no-effect.html [wpt.fyi]
- Event Timing: compare event timing interactionId for key press with no effect.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: compare event timing interactionId for key press with no effect.:
- /event-timing/interactionid-tap.html [wpt.fyi]:
TIMEOUT(Chrome:TIMEOUT, Safari:OK)- Event Timing: compare event timing interactionId for tap.:
TIMEOUT(Chrome:TIMEOUT, Safari:FAIL)
- Event Timing: compare event timing interactionId for tap.:
- /event-timing/only-observe-firstInput.html [wpt.fyi]
- Event Timing: check first-input for a PerformanceObserver observing only first-input.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: check first-input for a PerformanceObserver observing only first-input.:
- /event-timing/programmatic-click-not-observed.html [wpt.fyi]
- Event Timing: events from programmatic click are not observed:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: events from programmatic click are not observed:
- /event-timing/retrieve-firstInput.html [wpt.fyi]
- Event Timing: check first-input after onload, observer, click, click.:
FAIL(Chrome:PASS, Safari:FAIL)
- Event Timing: check first-input after onload, observer, click, click.:
- /layout-instability/input-timestamp.html [wpt.fyi]
- Layout shift right after user input is observable via PerformanceObserver.:
FAIL(Chrome:PASS, Safari:FAIL)
- Layout shift right after user input is observable via PerformanceObserver.:
- /layout-instability/recent-input.html [wpt.fyi]
- Layout shift right after user input is observable via PerformanceObserver.:
FAIL(Chrome:PASS, Safari:FAIL)
- Layout shift right after user input is observable via PerformanceObserver.:
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/41967a4ebec5 [wpt PR 35897] - Add keypress Event Timing Test, a=testonly
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
You need to log in
before you can comment on or make changes to this bug.
Description
•