- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 27 Jul 2010 09:44:07 -0700
- To: Sylvain Galineau <sylvaing@microsoft.com>
- Cc: Brad Kemper <brad.kemper@gmail.com>, Dennis Amrouche <dennis@screenlabor.de>, Brian Manthos <brianman@microsoft.com>, Aryeh Gregor <Simetrical+w3c@gmail.com>, "L. David Baron" <dbaron@dbaron.org>, Simon Fraser <smfr@me.com>, Brendan Kenny <bckenny@gmail.com>, www-style list <www-style@w3.org>
On Tue, Jul 27, 2010 at 9:27 AM, Sylvain Galineau <sylvaing@microsoft.com> wrote: > From: Tab Atkins Jr. [mailto:jackalmage@gmail.com] > Sent: Tuesday, July 27, 2010 7:50 AM > To: Sylvain Galineau > Cc: Brad Kemper; Dennis Amrouche; Brian Manthos; Aryeh Gregor; L. David Baron; Simon Fraser; Brendan Kenny; www-style list > Subject: Re: [css3-background] Where we are with Blur value discussion > >>I've suggested precisely what I think the criteria should be already. > > I'm not only asking what the criteria is but how it gets tested in a browser. > > Brad, for instance, does it with Photoshop. That's pretty cool but I don't think that's a reasonable answer for test suite purposes. Oh, gotcha. This is something that, unfortunately, requires testing abilities that we don't yet have in any framework. We can't reftest it because we're not requiring, and realistically can't require, pixel-perfection. We can't throw script at it, because there's no way right now to grab the pixels from a section of a page in a js-accessible way. (Hopefully we'll get that ability in <canvas> in the future.) We can automate it, we just have to build the automation manually - screenshot and then run pixel comparisons. ~TJ
Received on Tuesday, 27 July 2010 16:45:14 UTC