<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 9, 2009, at 4:19 PM, Gregg Tavares wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br><div class="gmail_quote">On Thu, Jul 9, 2009 at 4:11 PM, Oliver Hunt <span dir="ltr"><<a href="mailto:oliver@apple.com">oliver@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'd like to make a passionate plea that the spec say "implementations must<br>
support negative widths and negative heights and draw the image backward<br>
effectively flipping the result".<br>
</blockquote>
<br></div>
We'd need to be fairly sure that such a change would not break existing content -- this is a change that would result in substantially different rendering in some scenarios.<div class="im"></div></blockquote><div><br>
Given that it's inconsistent in the various browsers it's hard to see how this would break something since it's broken in 2 browsers one way or the other currently.<br></div></div></blockquote><div><br></div><div>Inconsistency doesn't lead to no one depending on a behaviour, it just means sites only work in one browser. Your suggesting would result in sites being broken in all browsers -- the only options from here on out are either nothing gets drawn (as in gecko and presto), or the destination is normalised (as in webkit)</div><br><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); margin-top: 0pt; margin-right: 0pt; margin-bottom: 0pt; margin-left: 0.8ex; padding-left: 1ex; position: static; z-index: auto; ">
Image scaling is implementation dependent everywhere else, why would it be spec defined in the case of canvas?</blockquote><div><br>There are 2 issues here I brought up<br><br>1) What happens at the edges. <br><br>The results are VASTLY different now. Unless this works consistently it would be hard to make canvas graphics work across browsers and expect get reproducible results. The 2x2 pixel example I gave, one browser ends up scaling with translucency even though there is no translucent pixels in the source image. <br></div></div></blockquote><div><br></div><div>This is just an artifact of scaling, and you agree below that scaling is implementation dependent.</div><br><blockquote type="cite"><div class="gmail_quote"><div>
<br>2) How it does the scaling. <br><br>I agree that it being implementation dependent is probably fine.<br><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font color="#888888">
<br>
--Oliver<br>
<br>
<br>
</font></blockquote></div><br>
</blockquote></div><br></body></html>