Created attachment 134883 [details] Results of CSS transition FPS tests for QT, Chrome, and Safari QGraphicsWebView has approx 10 less FPS for CSS transitions than Chrome/Safari on the same system. ### METHOD ### http://www.kaizou.org/code/kaizoumark/ measures CSS attribute changes at intervals to estimate FPS with CSS transitions in a variety of contexts. ### STEPS TO REPRODUCE ### Use the above tool in Safari, Chrome, and QTWebkit. The QTWebkit code is as follows: mainWindow::mainWindow(QWidget *parent) : QMainWindow(parent) { QGraphicsView* view = new QGraphicsView; view->setInteractive(true); setCentralWidget(view); QGraphicsScene* scene = new QGraphicsScene; view->setScene(scene); QGraphicsWebView* webView = new QGraphicsWebView; webView->setRenderHints(QPainter::Antialiasing & QPainter::HighQualityAntialiasing & QPainter::SmoothPixmapTransform & QPainter::TextAntialiasing & QPainter::NonCosmeticDefaultPen); scene->addItem(webView); QUrl url = QUrl::QUrl("http://www.kaizou.org/code/kaizoumark/"); webView->load(url); } ### RESULTS ### See attachment. A .png file with the results of each test, along with system information. Overall average is 24.4 FPS (QT), 35.5 FPS (Chrome), 34.9 FPS (Safari) ### ENVIRONMENT ### SDK: Qt SDK version 1.2 Chrome 18.0.1025.142 Safari 5.1.5 (7534.55.3) Processor 2.3 GHz Intel Core i5 Memory 4 GB 1333 MHz DDR3 Graphics Intel HD Graphics 3000 384 MB Software Mac OS X Lion 10.7.3 (11D50b)
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.