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

Unified Diff: third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/range-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/range-expected.txt
diff --git a/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/range-expected.txt b/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/range-expected.txt
deleted file mode 100644
index 23d87f03eee4620ec136deca02f9a7e67257961c..0000000000000000000000000000000000000000
--- a/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/forms/the-input-element/range-expected.txt
+++ /dev/null
@@ -1,25 +0,0 @@
-This is a testharness.js-based test.
-PASS range type support on input element
-PASS min attribute support on input element
-PASS max attribute support on input element
-FAIL Illegal value of min attribute assert_equals: expected "0" but got "ab"
-FAIL Illegal value of max attribute assert_equals: expected "100" but got "f"
-PASS Converting an illegal string to the default value
-FAIL Converting an illegal string to the default step assert_equals: expected "1" but got "xyz"
-PASS the value is set to min when a smaller value than min attribute is given
-PASS the value is set to max when a larger value than max attribute is given
-FAIL default value of min attribute in input type=range assert_equals: expected "0" but got ""
-FAIL default value of max attribute in input type=range assert_equals: expected "100" but got ""
-PASS default value when min and max attributes are given (= min plus half the difference between min and max)
-PASS default value with step control when both min and max attributes are given
-FAIL default value when both min and max attributes are given, while min > max assert_equals: expected "2" but got "51"
-PASS The default step scale factor is 1, unless min attribute has non-integer value
-PASS Step scale factor behavior when min attribute has integer value but max attribute is non-integer
-FAIL The default scale factor is 1 even if step attribute is explicitly set to non-integer value, unless min attribute has non-integer value assert_equals: expected "1" but got "0.5"
-PASS Solving the step mismatch
-PASS Performing stepUp()
-PASS Performing stepDown()
-PASS Performing stepUp() beyond the value of the max attribute
-PASS Performing stepDown() beyond the value of the min attribute
-Harness: the test ran to completion.
-

Powered by Google App Engine
This is Rietveld 408576698