- From: <bugzilla@jessica.w3.org>
- Date: Thu, 24 Jan 2013 16:39:05 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19905 Jay Munro <jaymunro@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Jay Munro <jaymunro@microsoft.com> --- Ok, to summarize: 1. create a linear-gradient that lets you set an angle and color stops. Q. how does this improve the use of createLinearGradient, and individual color stops? It seems to make a longer single line, rather than a more readable individual lines. (gradient.addColorStop("0", "magenta"), gradient.addColorStop(".50","yellow"), etc... What key words do you see for angle or side to corner. You've got "to bottom", are there others and how would they operate? 2. A simpler transform that takes rotation and translate parameters, instead of only a matrix, as well as degrees rather than radians. Sounds handy. I'd add-in for rotate having an optional setting of center point of rotation (rotate(45deg,100,100). 3. Canvas object with optional width and height parameters. I like that one. Without the extra parameters, it would be default (300x150?), correct? 4. Giving colors as either a hex block or a text color value, plus transparency (alpha channel). This looks like a quick way to set a color value other than full alpha, since rgba() can substitute for a color value in most situations. Good idea, though I wonder what the perf hit would be for implementers to parse before applying the alpha. Lets toss it out there and see what people think. Assigning to myself to track. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 24 January 2013 16:39:10 UTC