[webkit-qt] accelerated compositing

[Antti Koivisto]

I think it should be enabled by default. It is a feature that requires
special triggers (css transformations, animations) to get enabled so
it won't affect most of the existing content. The only way we are
going to find problems is by having people run it.


   antti

On Fri, Mar 19, 2010 at 11:51 AM, Simon Hausmann
<simon.hausmann at nokia.com> wrote:
> 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
>
> _______________________________________________
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>
>