This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ideas:color-object [2014/07/09 09:54] – Lingering ref to "CSSColor" tabatkins | ideas:color-object [2014/07/10 02:08] – <code idl> crissov | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | <code idl> | ||
[Constructor(double r, double g, double b, optional double a=1), | [Constructor(double r, double g, double b, optional double a=1), | ||
| | ||
Line 14: | Line 15: | ||
static RGBAColor fromHex(octet r, octet g, octet b, optional octet a=255); | static RGBAColor fromHex(octet r, octet g, octet b, optional octet a=255); | ||
static RGBAColor fromHex(optional HexColorInit color); | static RGBAColor fromHex(optional HexColorInit color); | ||
+ | | ||
+ | DOMString? asKeyword(); | ||
+ | /* Add fromKeyword()? | ||
| | ||
DOMString toString(optional DOMString type=" | DOMString toString(optional DOMString type=" | ||
static readonly attribute Map serializationTypes; | static readonly attribute Map serializationTypes; | ||
}; | }; | ||
+ | </ | ||
- | 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. | + | The '' |
- | Authors can define their own color formats by adding a fromFoo() to RGBAColor, a toFoo() to RGBAColor.prototype, | + | Authors can define their own color formats by adding a '' |
+ | <code idl> | ||
dictionary RGBAColorInit { | dictionary RGBAColorInit { | ||
double r = 0; | double r = 0; | ||
Line 47: | Line 53: | ||
RGBAColor parseColor(DOMString color, optional Element el); | RGBAColor parseColor(DOMString color, optional Element el); | ||
}; | }; | ||
+ | </ | ||
+ | |||
+ | '' | ||
- | If parseColor | + | The optional second argument |
- | such as '' | + | |
- | but no el argument | + | |
- | throw a XXX error. | + |