27313 2014-11-12 12:23:18 +0000 It seems like this should be defined in terms of an IDL enum. If not, please clarify the relationshi [...] 2018-01-29 14:33:14 +0000 1 1 1 Unclassified CSS Compositing unspecified Other other NEW https://html.spec.whatwg.org/#dom-context-2d-globalcompositeoperation P3 normal --- 1 contributor cabanier annevk cabanier cabanier ian mike public-css-bugzilla oldest_to_newest 114836 0 contributor 2014-11-12 12:23:18 +0000 Specification: https://html.spec.whatwg.org/multipage/scripting.html Multipage: https://html.spec.whatwg.org/multipage/#dom-context-2d-globalcompositeoperation Complete: https://html.spec.whatwg.org/#dom-context-2d-globalcompositeoperation Referrer: https://html.spec.whatwg.org/multipage/ Comment: It seems like this should be defined in terms of an IDL enum. If not, please clarify the relationship to the referenced document as it does not define canonical names. E.g. I believe in browsers you need to use "xor", not "XOR". Posted from: 46.127.136.57 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:36.0) Gecko/20100101 Firefox/36.0 114860 1 ian 2014-11-12 19:15:56 +0000 The spec says: "These values are all case-sensitive — they must be used exactly as defined. User agents must not recognise values that are not a case-sensitive match for one of the values given in the Compositing and Blending specification." Is there more that you need here? Defining this as an Enum is something that could be done, but it should be done in the Compositing and Blending specification, where the keywords are defined. 114863 2 annevk 2014-11-12 19:56:37 +0000 But that specification has the wrong casing as far as I can tell. I remember all globalCompositeOperation keywords being lowercase. 114866 3 cabanier 2014-11-12 20:32:23 +0000 (In reply to Anne from comment #2) > But that specification has the wrong casing as far as I can tell. I remember > all globalCompositeOperation keywords being lowercase. where do you see that they are not lowercase? 114867 4 annevk 2014-11-12 20:38:52 +0000 E.g. http://dev.w3.org/fxtf/compositing-1/#porterduffcompositingoperators_xor 114868 5 cabanier 2014-11-12 20:40:31 +0000 (In reply to Anne from comment #4) > E.g. http://dev.w3.org/fxtf/compositing-1/#porterduffcompositingoperators_xor Those are the descriptions of the algorithms. The values are described here: http://dev.w3.org/fxtf/compositing-1/#canvascompositingandblending 114869 6 annevk 2014-11-12 20:45:10 +0000 If you define them in terms of CSS, should CSS escapes now work? Should they be case-insensitive rather than what Ian just said? I don't think this works. 114874 7 ian 2014-11-12 23:02:19 +0000 Yeah that spec should be fixed to define the API surface, not just CSS. 129057 8 annevk 2018-01-29 14:33:14 +0000 Filed https://github.com/w3c/fxtf-drafts/issues/252.