<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 23, 2010, at 12:43 PM, Tab Atkins Jr. wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; "> Implementors, does<br>this sounds like a change you can get behind? We already changed<br>canvas shadows to match behavior with CSS shadows; this is a much<br>smaller change for spec-equivalence.</span></span></blockquote></div><br><div>This would be hard for WebKit, which relies on Core Graphics for gradients</div><div>on some platforms. CG doesn't allow us to interpolate in premultiplied space.</div><div><br></div><div>[Of course, some of the new radial gradient stuff is also not doable using</div><div>CG, so maybe we'll have to have a slower non-CG gradient code</div><div>path anyway].</div><div><br></div><div>Simon</div><div><br></div></body></html>