On Fri, 10 Jun 2011, Chris Jones wrote:
In 2D canvas, determining whether a point is inside a path is
currently always done using the non-zero winding rule. I propose
extending 2D canvas to allow determining inside-ness using the even-odd
rule.
I've added this to the spec.
On Wed, 2
On Thu, Jan 3, 2013 at 3:38 PM, Ian Hickson i...@hixie.ch wrote:
On Fri, 10 Jun 2011, Chris Jones wrote:
In 2D canvas, determining whether a point is inside a path is
currently always done using the non-zero winding rule. I propose
extending 2D canvas to allow determining inside-ness
On Tue, Dec 11, 2012 at 9:04 AM, Ian Hickson i...@hixie.ch wrote:
On Tue, 11 Dec 2012, Gregg Tavares (社ç~T¨) wrote:
discussion seems to have died down here but I'd like to bring up another
issue
In WebGL land we have creation attributes on the drawingbuffer made for a
canvas. Example
On Thu, 3 Jan 2013, Rik Cabanier wrote:
I have made it be part of the graphics state in the spec; it would be
unusual in the API for it not to be. However, if this doesn't match
implementations, please let me know.
Do you mean browser implementations or graphic libraries? AFAIK all
On Thu, Jan 3, 2013 at 4:58 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 3 Jan 2013, Rik Cabanier wrote:
I have made it be part of the graphics state in the spec; it would be
unusual in the API for it not to be. However, if this doesn't match
implementations, please let me know.
On Thu, Jan 3, 2013 at 6:49 PM, Ian Hickson i...@hixie.ch wrote:
As an aside, it's odd that if images are unsupported or disabled, no
event is fired at all (update the image data, step 4). That means
that if you do this:
var url = URL.createObjectURL(blob);
img.src = url;
On Thu, 3 Jan 2013, Glenn Maynard wrote:
It might make sense to fire onerror if the image doesn't get loaded
because images are disabled. Guaranteeing (or coming closer to
guaranteeing, at least) that onload or onerror will always be fired
would reduce the differences in event flow when
