On Friday 19 March 2010 ext Antti Koivisto, wrote:
> 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.

People _can_ run it, and we should ask people to try it out. That's why it's 
also a run-time option in QtLauncher for example. But should we really enable 
it by default, given that it has zero test coverage?


Simon

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
webkit-qt mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Reply via email to