[webkit-dev] Test frame size for reftests

Dirk Pranke dpranke at chromium.org
Wed Apr 24 11:11:44 PDT 2013

On Wed, Apr 24, 2013 at 10:30 AM, L. David Baron <dbaron at dbaron.org> wrote:

> On Wednesday 2013-04-24 09:55 -0700, Darin Adler wrote:
> > On Apr 23, 2013, at 11:36 AM, Benjamin Poulain <benjamin at webkit.org>
> wrote:
> >
> > > The current mode works fine for some ref-tests but is really annoying
> for others. I would love to have a way to compare the entire page instead
> of the viewport.
> > >
> > > Maybe it could just be an API on testrunner? Like:
> > >     testRunner.dumpEntirePagePixels()?
> >
> > What’s the downside of just doing this for all reftests? Would it
> > make them slower? Would it cause failures? I’d love it if we could
> > just do it without it having to be opt-in.
> Tests that rely on this wouldn't be sharable with other browsers or
> usable in W3C test suites, at least based on current practice.
> (I think we had some sort of agreement within some set of people
> involved with W3C reftests to use 800x600.  Mozilla is currently
> using 800x1000, though I'd like to switch to the smaller size.)
I think this raises two related questions, both of which would be helped by
concrete examples:

1) What sort of test are you writing where 800x600 isn't big enough to test
what you need to test?

2) What sort of test are you writing where there's needs to be something on
the page not included in the test
*and* will render differently in different browsers?

I can posit the existence of both sorts of things, but I'm not sure when
they arise in practice?

-- Dirk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20130424/2cd1870b/attachment.html>

More information about the webkit-dev mailing list