Closed Bug 1892346 Opened 1 years ago Closed 1 years ago

[wpt-sync] Sync PR 45792 - Support :user-valid/:user-invalid on multifield inputs

Categories

(Core :: CSS Parsing and Computation, task, P4)

task

Tracking

()

RESOLVED FIXED
127 Branch
Tracking Status
firefox127 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 45792 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/45792
Details from upstream follow.

Joey Arhar <jarhar@chromium.org> wrote:

Support :user-valid/:user-invalid on multifield inputs

This patch makes :user-valid and :user-invalid start working on inputs
with type date, datetime-local, and time. I matched the webkit behavior
for when to start matching in response to keyboard input.

Fixed: 328674226
Change-Id: If3c394e43043a0b3d27eac22d0671c6b45b82bc6

Reviewed-on: https://chromium-review.googlesource.com/5463293
WPT-Export-Revision: f6e12ad88b52a6f6592ac19427c3509ee33df09c

Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 3 tests and 4 subtests

Status Summary

Firefox

OK : 3
PASS: 9
FAIL: 5

Chrome

OK : 3
PASS: 9
FAIL: 5

Safari

OK : 3
PASS: 11
FAIL: 3

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/3619c39134fb [wpt PR 45792] - Support :user-valid/:user-invalid on multifield inputs, a=testonly https://hg.mozilla.org/integration/autoland/rev/1b01036514a2 [wpt PR 45792] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 years ago
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
You need to log in before you can comment on or make changes to this bug.