[webkit-dev] Using ref tests for repaint bugs
zandobersek at gmail.com
Fri May 25 13:42:11 PDT 2012
On Fri, May 25, 2012 at 9:57 AM, Dominik Röttsches <
dominik.rottsches at intel.com> wrote:
> On 05/25/2012 02:43 AM, Andrei Bucur wrote:
> As Simon states, some repaint tests will likely not be possible to write
> correctly as ref tests, but some of them I think they fit very well in the
> happy-no-pixel-test bucket :). If people decide it's a direction worth
> investigating, I'll give the idea a spin.
> I'd be interested to hear about your progress. Recently I was facing a
> couple of similar issues:
> and then GTK decided to always do repaints before dumping pixel results:
> which might not be the right solution either - so if you come up with
> something more fine-grained - that'd be great.
Here's why a repaint is forced for the Gtk port before dumping pixel
Gtk port uses a backing store which is updated every 0.0166667 seconds,
i.e. 60 times per second, a reasonable interval. The problem is that many
tests are structured in the way that they make an alteration that produces
a layout change and then immediately finish. This leaves no time for the
backing store to be updated. It would also be ridiculous to go around
fixing tests by delaying the finish by any amount of time.
Because of that a repaint is forced just before dumping the pixel results
so the dirty regions of the backing store (only those and not the complete
backing store) are updated.
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev