[webkit-qt] accelerated compositing

[Simon Hausmann]

Hi,

I was one of the people in favour of enabling this feature by default, and I'm 
also guilty for the patch to toggle it. I say guilty because I changed my 
opinion, after I had a long chat with Benjamin.

Currently we have

    1) no automated functional tests
    2) no automated performance tests

for a big feature that improves performance. We have clear evidence of it 
improving performance with manual testing - I've seen it myself and I love it. 

But what do we have in place to protect ourselves from regressions or 
situations where it actually slows down rendering or causes misrenderings?

I'm concerned that without automated tests we run a very high risk of 
regressing, for a feature we put a lot of bets on.

A lot of efforts went into improving the functional testing (DRT) and the 
performance framework, in the past few months. Let's use some of that 
infrastructure first to gain more confidence in the feature and to protect 
ourselves from regressions, before we enable it by default.

What do you think?


Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.webkit.org/pipermail/webkit-qt/attachments/20100319/22944f70/attachment.bin>