On Jan 10, 2013, at 8:10 AM, Rik Cabanier <[email protected]> wrote:
> > > On Wed, Jan 9, 2013 at 10:36 PM, Dirk Schulze <[email protected]> wrote: > > > On Jan 9, 2013, at 9:29 PM, "Rik Cabanier" <[email protected]> wrote: > >> Hi Dirk, >> >> the 'globalCompositeOperation' property takes the same syntax as the css >> 'mix' so I don't think an enum will work. >> > > I am not following. What does the CSS property have to do with the canvas > attribute? > > > See the spec: > https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#canvascompositingandblending > For consistency, people wanted the same syntax for canvas and css. > That is fine for me. I am not asking for different values or keyword names :P Dirk > >> Rik >> >> On Wed, Jan 9, 2013 at 6:18 PM, Dirk Schulze <[email protected]> wrote: >> Hi, >> >> After all the discussions about winding rules and the new introduced >> enumeration for "nonzero" and "even odd", I wonder if the the compositing >> and blending modes should be two enumerations as well. >> >> enum CanvasCompositingMode { >> "source-over", >> "source-in", >> … >> } >> >> and >> >> enum CanvasBlendingMode { >> "normal", >> "multiply", >> ... >> } >> >> This wouldn't actually change the behavior or definition a lot, but might >> help to cleanup a bit. I am happy about other names if they are not good >> enough. >> >> Greetings, >> Dirk >> >
