<span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; color: rgb(80, 0, 80); "><font class="Apple-style-span" color="#000000">People have a very strong feeling about Firefox. This is beautiful, but not good to it. Firefox is now, over the Windows 7 and Mac, the slowest browser. Just pick some JavaScripts and test. XUL is the most hard way for builting an extension and Firefox eats CPU when we run any game built using HTML Elements.</font><div>
<font class="Apple-style-span" color="#000000"><br></font></div><div><font class="Apple-style-span" color="#000000">But this is not the point.</font></div><div><font class="Apple-style-span" color="#000000"><br></font></div>
<div><b><font class="Apple-style-span" color="#000000">"</font></b><span style="font-family: sans-serif, 'Droid Sans Fallback'; font-size: medium; line-height: 21px; "><b><font class="Apple-style-span" color="#000000">Composite </font></b><var title=""><b><span style="font-style: normal; "><font class="Apple-style-span" color="#000000">A</font></span></b></var><b><font class="Apple-style-span" color="#000000"> within the clipping region over the current canvas bitmap using the current composition operator."</font></b></span></div>
<div><span style="font-family: sans-serif, 'Droid Sans Fallback'; font-size: medium; line-height: 21px; "><b><font class="Apple-style-span" color="#000000"><br></font></b></span></div><div><font face="sans-serif, 'Droid Sans Fallback'"><span style="line-height: 21px; font-size: medium; "><span style="font-size: small; "><font class="Apple-style-span" color="#000000">The word "clipping" is the point. I am very sad that input type="color" does not cite the need of a color picker. But This part, is completely bright.</font></span></span></font></div>
<div><font face="sans-serif, 'Droid Sans Fallback'"><span style="line-height: 21px; font-size: medium; "><span style="font-size: small; "><font class="Apple-style-span" color="#000000"><br></font></span></span></font></div>
<div><font face="sans-serif, 'Droid Sans Fallback'"><span style="line-height: 21px; font-size: medium; "><span style="font-size: small; "><font class="Apple-style-span" color="#000000">That's why Microsoft agree with Chrome, Chrome with Safari (they don't agree sometimes) and Opera presents that way too.</font></span></span></font></div>
<div><font face="sans-serif, 'Droid Sans Fallback'"><span style="line-height: 21px; font-size: medium; "><span style="font-size: small; "><font class="Apple-style-span" color="#000000"><br></font></span></span></font></div>
<div><font face="sans-serif, 'Droid Sans Fallback'"><span style="line-height: 21px; font-size: medium; "><span style="font-size: small; "><font class="Apple-style-span" color="#000000">A hug.</font></span></span></font></div>
</span><br><div class="gmail_quote">2010/7/29 David Flanagan <span dir="ltr"><<a href="mailto:david@davidflanagan.com">david@davidflanagan.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
James Robinson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Wed, Jul 28, 2010 at 2:46 PM, Tab Atkins Jr. <<a href="mailto:jackalmage@gmail.com" target="_blank">jackalmage@gmail.com</a> <mailto:<a href="mailto:jackalmage@gmail.com" target="_blank">jackalmage@gmail.com</a>>> wrote:<br>
<br>
On Wed, Jul 28, 2010 at 2:43 PM, David Flanagan<br></div><div class="im">
<<a href="mailto:david@davidflanagan.com" target="_blank">david@davidflanagan.com</a> <mailto:<a href="mailto:david@davidflanagan.com" target="_blank">david@davidflanagan.com</a>>> wrote:<br>
> Firefox and Chrome disagree about the implementation of the<br>
> destination-atop, source-in, destination-in, and source-out<br>
compositing<br>
> operators. Test code is attached.<br>
<br>
<br>
I don't think your attachment made it through. <a href="https://developer.mozilla.org/samples/canvas-tutorial/6_1_canvas_composite.html" target="_blank">https://developer.mozilla.org/samples/canvas-tutorial/6_1_canvas_composite.html</a> shows some of the differences, although it does not cover all cases.<br>
</div></blockquote>
<br>
You didn't miss much. My example was very similar to the one you link to.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The spec is certainly clear but that does not make the behavior it specifies good. I find the spec's behavior pretty bizarre and Microsoft has expressed a preference for the Safari/Chrome interpretation: <a href="http://lists.w3.org/Archives/Public/public-canvas-api/2010AprJun/0046.html" target="_blank">http://lists.w3.org/Archives/Public/public-canvas-api/2010AprJun/0046.html</a> - although that thread did not get much discussion. <br>
</blockquote>
<br></div>
Thanks for that link. The thread you reference refers back to an earlier thread on this list. My apologies for not finding it and reading it before posting again.<div class="im"><br>
<br>
For example, I think<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
drawing a 20x20 image into a 500x500 canvas without scaling with a globalCompositeOperation of 'copy' should result in only the 20x20 region being cleared out, not the entire canvas.<br>
</blockquote>
<br></div>
Yikes! It hadn't occurred to me that copy should behave that way. But you're right that that is what the spec requires. Opera does it that way. Firefox, thankfully, does not.<br>
<br>
Perhaps independently of the debate over infinite bitmap vs. shape extents, we can agree that "copy" is a special value that means "do not perform compositing"<br><font color="#888888">
<br>
David<br>
</font></blockquote></div><br>