h5bp/html5please — comment on commit 6132ace84067de3ad4cf8005d030d92a60c7330c
File:  line 0
By bentruyman:

As someone with a bit of experience using FlashCanvas spending a number of hours tracing through Actionscript, I'm on the fence as to whether or not `canvas` should be classified as "use" or "caution". It isn't a drop-in polyfill that's going to transparently produce the kind of results we typically expect from most polyfills. FlashCanvas, in my experience, handles basic shapes and simple animations just fine. But as soon as you take it outside of it's narrow comfort zone, it falls apart.

It's not a polyfill I'd be able to make even a semi-complex game on, for example. Nor would I bother running something like a particle generator on it. I apologize I don't have a more complex example to prove my point. :(

Also, I should note, the author of the project states that FlashCanvas' does fairly well when put up against [this test suite](http://philip.html5.org/tests/canvas/suite/tests/), which it does. However, where FlashCanvas often fails is when you actually throw it into a real-world situation where we're performing a several operations on the canvas at once (like a `globalCompositionOperation` on a `drawImage`).

tl;dr Without a better alternative than FlashCanvas, I'd say this one should be classified as "caution".