RESOLVED FIXED 110751
[Qt][WK2] Remove unneeded method didResumeContent from PageViewportController clients
https://bugs.webkit.org/show_bug.cgi?id=110751
Summary [Qt][WK2] Remove unneeded method didResumeContent from PageViewportController...
Andras Becsi
Reported 2013-02-25 05:27:43 PST
[Qt][WK2] Remove unneeded method didResumeContent from PageViewportController clients
Attachments
Patch (7.23 KB, patch)
2013-02-25 05:28 PST, Andras Becsi
no flags
Andras Becsi
Comment 1 2013-02-25 05:28:30 PST
Jocelyn Turcotte
Comment 2 2013-02-25 05:54:09 PST
Comment on attachment 190041 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=190041&action=review > Source/WebKit2/UIProcess/PageViewportController.cpp:320 > if (!m_hasSuspendedContent) > return; Cool, the only purpose I then see left of suspend/resumeContent in PageViewportController is headed by the following comment in pageDidRequestScroll: // Ignore the request if suspended. Can only happen due to delay in event delivery. So do you think we could go even further and remove all knowledge of page suspension in PVC?
Andras Becsi
Comment 3 2013-02-25 06:16:37 PST
Comment on attachment 190041 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=190041&action=review >> Source/WebKit2/UIProcess/PageViewportController.cpp:320 >> return; > > Cool, the only purpose I then see left of suspend/resumeContent in PageViewportController is headed by the following comment in pageDidRequestScroll: > // Ignore the request if suspended. Can only happen due to delay in event delivery. > > So do you think we could go even further and remove all knowledge of page suspension in PVC? I'll check. I think we can, since the WebPageProxy already has early returns to not send unnecessary events.
Andras Becsi
Comment 4 2013-02-25 06:21:01 PST
(In reply to comment #3) > (From update of attachment 190041 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=190041&action=review > > >> Source/WebKit2/UIProcess/PageViewportController.cpp:320 > >> return; > > > > Cool, the only purpose I then see left of suspend/resumeContent in PageViewportController is headed by the following comment in pageDidRequestScroll: > > // Ignore the request if suspended. Can only happen due to delay in event delivery. > > > > So do you think we could go even further and remove all knowledge of page suspension in PVC? > > I'll check. I think we can, since the WebPageProxy already has early returns to not send unnecessary events. Actually there are references to m_controller->hasSuspendedContent() from the client (at least for Qt).
Andras Becsi
Comment 5 2013-02-25 06:34:43 PST
(In reply to comment #4) > (In reply to comment #3) > > (From update of attachment 190041 [details] [details]) > > View in context: https://bugs.webkit.org/attachment.cgi?id=190041&action=review > > > > >> Source/WebKit2/UIProcess/PageViewportController.cpp:320 > > >> return; > > > > > > Cool, the only purpose I then see left of suspend/resumeContent in PageViewportController is headed by the following comment in pageDidRequestScroll: > > > // Ignore the request if suspended. Can only happen due to delay in event delivery. > > > > > > So do you think we could go even further and remove all knowledge of page suspension in PVC? > > > > I'll check. I think we can, since the WebPageProxy already has early returns to not send unnecessary events. > > Actually there are references to m_controller->hasSuspendedContent() from the client (at least for Qt). On second thought, it looks like only PageViewportControllerClientQt::didChangeContentsSize really depend on knowing about the suspend state, all the other references could be substituted with checking if the scale animation is active. Let's see.
Andras Becsi
Comment 6 2013-02-25 07:49:30 PST
(In reply to comment #2) > (From update of attachment 190041 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=190041&action=review > > > Source/WebKit2/UIProcess/PageViewportController.cpp:320 > > if (!m_hasSuspendedContent) > > return; > > Cool, the only purpose I then see left of suspend/resumeContent in PageViewportController is headed by the following comment in pageDidRequestScroll: > // Ignore the request if suspended. Can only happen due to delay in event delivery. I is also happening when there are mouse wheel events during a double tap to zoom animation, so the comment is not completely accurate. > > So do you think we could go even further and remove all knowledge of page suspension in PVC? As discussed on IRC, we can try to make the PVC slimmer, or event merge the shareable functionality somewhere reasonable later, once we know where things are heading with the shared WebView and and specific API.
Jocelyn Turcotte
Comment 7 2013-02-25 08:12:46 PST
Comment on attachment 190041 [details] Patch Looks good then, r=me
Andras Becsi
Comment 8 2013-02-25 09:15:50 PST
Comment on attachment 190041 [details] Patch Clearing flags on attachment: 190041 Committed r143935: <http://trac.webkit.org/changeset/143935>
Andras Becsi
Comment 9 2013-02-25 09:15:56 PST
All reviewed patches have been landed. Closing bug.
Zoltan Arvai
Comment 10 2013-02-26 04:22:30 PST
Please check API tests: Before the patch: 189 passed, 3 failed, 0 skipped, 0 crashed http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/builds/14249 After the patch: 182 passed, 10 failed, 0 skipped, 0 crashed http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/builds/14250
Andras Becsi
Comment 11 2013-02-26 05:17:53 PST
(In reply to comment #10) > Please check API tests: > > Before the patch: > 189 passed, 3 failed, 0 skipped, 0 crashed > http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/builds/14249 > > After the patch: > 182 passed, 10 failed, 0 skipped, 0 crashed > http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/builds/14250 Thanks. Investigating.
Andras Becsi
Comment 12 2013-02-28 09:55:34 PST
(In reply to comment #11) > (In reply to comment #10) > > Please check API tests: > > > > Before the patch: > > 189 passed, 3 failed, 0 skipped, 0 crashed > > http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/builds/14249 > > > > After the patch: > > 182 passed, 10 failed, 0 skipped, 0 crashed > > http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Amazon%20EC2%29/builds/14250 > > Thanks. Investigating. Fixed in https://bugs.webkit.org/show_bug.cgi?id=111086
Note You need to log in before you can comment on or make changes to this bug.