[Typed OM] Add CSSValue -> CSSNumberValue conversion

third_party/WebKit/LayoutTests/typedcssom/inlinestyle/numbers-expected.txt

Index: third_party/WebKit/LayoutTests/typedcssom/inlinestyle/numbers-expected.txt
diff --git a/third_party/WebKit/LayoutTests/typedcssom/inlinestyle/numbers-expected.txt b/third_party/WebKit/LayoutTests/typedcssom/inlinestyle/numbers-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..b5567dd228e5f18bc0f75aca6263f58b61b14e7d
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/typedcssom/inlinestyle/numbers-expected.txt
@@ -0,0 +1,7 @@
+This is a testharness.js-based test.
+PASS CSSNumberValue round trips when passed in as CSSNumberValue. 
+PASS CSSNumberValue round trips when passed as a string to the old OM. 
+FAIL CSSNumberValues in a list round trip when passed in as a list of CSSNumberValues assert_equals: expected "1, 5.5" but got "1 5.5"

[sashab, 2016/07/11 23:47:22]

??? Is this correct?

[meade_UTC10, 2016/07/27 07:14:29]

It's a consequence of the TODO you commented on. I figured having an expectation
is better than not writing a test at all... to be fixed in a future CL!

[sashab, 2016/07/27 23:23:57]

That's a great idea! :D Except I think this should be using TestHarness.js.

I think the best way to do this would be:
1. Split out numbers.html into its own test
2. Make a new test numbers-non-space-separator.html which fails
3. Add a failing test expectation to TestExpectations with a bug and a comment
like "Expected to fail until CSSOM types know the correct separator for list
properties."

[Timothy Loh, 2016/07/28 02:11:31]

Please don't add new entries to TestExpectations. This sort of expected.txt file
is fine.

[meade_UTC10, 2016/08/03 03:26:44]

I don't think it makes sense to split this test up just to merge it again later
after making the separator change.

+PASS CSSNumberValues in a list round trip when passed in as a string to the old OM 
+Harness: the test ran to completion.
+