Differences

This shows you the differences between two versions of the page.

--- ideas:color-object [2014/07/07 18:32] – fix return values tabatkins
+++ ideas:color-object [2014/07/09 19:24] – Reword parseColor() definition. tabatkins
@@ Line 15: / Line 15: @@
     static RGBAColor fromHex(optional HexColorInit color);
-    stringifier DOMString (optional DOMString type="rgba");
+    DOMString toString(optional DOMString type="rgba");
     static readonly attribute Map serializationTypes;
   };
-The stringifier looks up the type in the RGBAColor.serializationTypes Map; if it finds a function, it calls that with the RGBAColor as the sole argument and returns whatever the function returns.  It's preloaded with UA-defined functions for "hex3", "hex6", "rgb", "rgba", "hsl", and "hsla".
+The toString() method looks up the type in the RGBAColor.serializationTypes Map; if it finds a function, it calls that with the RGBAColor as the sole argument and returns whatever the function returns.  It's preloaded with UA-defined functions for "hex3", "hex6", "rgb", "rgba", "hsl", and "hsla".
 Authors can define their own color formats by adding a fromFoo() to RGBAColor, a toFoo() to RGBAColor.prototype, and adding an appropriate serialization tag to RGBAColor.serializationTypes.
@@ Line 45: / Line 45: @@
   partial interface CSS {
-    CSSColor parseColor(DOMString color, optional Element el);
+    RGBAColor parseColor(DOMString color, optional Element el);
   };
-If parseColor is called with a color that depends on the element on which it is used,
+parseColor() takes a string containing any CSS color, and returns an RGBAColor for it.  If the string isn't parseable as a color, throw a SyntaxError exception.
-such as ''currentcolor'' or ''inherit'',
-but no el argument was passed,
+The optional second argument is used to resolve colors that vary based on the element, such as ''currentcolor''.  If such a color is parsed but the second argument is not provided, throw a XXX exception.
-throw a XXX error.