Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(11)

Unified Diff: third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/datetime-2-expected.txt

Issue 1984023002: Move web-platform-tests to wpt (part 1 of 2) (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/datetime-2-expected.txt
diff --git a/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/datetime-2-expected.txt b/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/datetime-2-expected.txt
deleted file mode 100644
index 0e26dab21c192aa1d9939a0d1dae01fc07c49f24..0000000000000000000000000000000000000000
--- a/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/datetime-2-expected.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-This is a testharness.js-based test.
-PASS empty value
-PASS datetime input value set to 2014-01-01T11:11Z without min/max
-FAIL datetime input value set to 2014-01-01 11:11Z without min/max assert_equals: expected "2014-01-01T11:11Z" but got "2014-01-01 11:11Z"
-FAIL datetime input value set to 2014-01-01 11:11-04:00 without min/max assert_equals: expected "2014-01-01T15:11Z" but got "2014-01-01 11:11-04:00"
-FAIL datetime input value set to 2014-01-01 11:11-0400 without min/max assert_equals: expected "2014-01-01T15:11Z" but got "2014-01-01 11:11-0400"
-FAIL datetime input value set to 2014-01-01 11:11:00.000-04:00 without min/max assert_equals: expected "2014-01-01T15:11Z" but got "2014-01-01 11:11:00.000-04:00"
-FAIL datetime input value set to 2014-01-01 11:11:00.000Z without min/max assert_equals: expected "" but got "2014-01-01 11:11:00.000Z"
-FAIL datetime input value set to 2014-01-01 11:11:00.000 without min/max assert_equals: expected "" but got "2014-01-01 11:11:00.000"
-FAIL datetime input value set to 2014-01-01 11:11:00.000+ without min/max assert_equals: expected "" but got "2014-01-01 11:11:00.000+"
-FAIL datetime input value set to 2014-01-01 11:11:00.000+24 without min/max assert_equals: expected "" but got "2014-01-01 11:11:00.000+24"
-FAIL datetime input value set to 2014-01-01 11:11:00.000+2360 without min/max assert_equals: expected "" but got "2014-01-01 11:11:00.000+2360"
-FAIL datetime input value set to 2014-01-0 11:11:00.000+0400 without min/max assert_equals: expected "" but got "2014-01-0 11:11:00.000+0400"
-FAIL datetime input value set to 2014-01-01 11:1:00.000+0400 without min/max assert_equals: expected "" but got "2014-01-01 11:1:00.000+0400"
-FAIL Value >= min attribute assert_equals: expected "2014-01-01T11:11Z" but got "2014-01-01 11:11Z"
-FAIL Value < min attribute assert_equals: expected "2014-01-01T11:11Z" but got "2014-01-01 11:10Z"
-FAIL Value <= max attribute assert_equals: expected "2014-01-01T11:11Z" but got "2014-01-01 11:10Z"
-FAIL Value > max attribute assert_equals: expected "2014-01-01T11:10Z" but got "2014-01-01 11:11Z"
-Harness: the test ran to completion.
-

Powered by Google App Engine
This is Rietveld 408576698