RESOLVED FIXED 85088
[Qt][WK2] Don't call syncRemoteContents from WebLayerTreeRenderer::paintToCurrentGLContext
https://bugs.webkit.org/show_bug.cgi?id=85088
Summary [Qt][WK2] Don't call syncRemoteContents from WebLayerTreeRenderer::paintToCur...
Yael
Reported 2012-04-27 11:50:35 PDT
It has recently moved to QQuickWebPage::updatePaintNode.
Attachments
Patch. (2.29 KB, patch)
2012-04-27 12:08 PDT, Yael
no flags
Yael
Comment 1 2012-04-27 12:08:33 PDT
Jocelyn Turcotte
Comment 2 2012-04-27 12:28:07 PDT
Comment on attachment 139245 [details] Patch. View in context: https://bugs.webkit.org/attachment.cgi?id=139245&action=review > Source/WebKit2/UIProcess/API/qt/qquickwebview.cpp:786 > + > + // Ensure that updatePaintNode is always called before painting. > + pageView->update(); This change should go in your fixed element patch and not here, since it is the one that is going to add code in updatePaintNode that must be called when the viewport move.
Yael
Comment 3 2012-04-27 12:48:42 PDT
(In reply to comment #2) > (From update of attachment 139245 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=139245&action=review > > > Source/WebKit2/UIProcess/API/qt/qquickwebview.cpp:786 > > + > > + // Ensure that updatePaintNode is always called before painting. > > + pageView->update(); > > This change should go in your fixed element patch and not here, since it is the one that is going to add code in updatePaintNode that must be called when the viewport move. Existing fixed position tests are breaking without this change. I cannot remove syncRemoteContents without adding this.
Noam Rosenthal
Comment 4 2012-04-27 12:57:05 PDT
Comment on attachment 139245 [details] Patch. LGTM, I agree with yael's comment.
WebKit Review Bot
Comment 5 2012-04-27 16:48:15 PDT
Comment on attachment 139245 [details] Patch. Clearing flags on attachment: 139245 Committed r115515: <http://trac.webkit.org/changeset/115515>
WebKit Review Bot
Comment 6 2012-04-27 16:48:19 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.