Bug 130301

Summary: element.click does synchronous IPC to get the screenRect.
Product: WebKit Reporter: Andreas Kling <kling>
Component: WebKit2Assignee: Darin Adler <darin>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: buildbot, kling, rniwa
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
First cut
buildbot: commit-queue-
Archive of layout-test-results from webkit-ews-14 for mac-mountainlion-wk2 none

Description Andreas Kling 2014-03-15 23:54:30 PDT
Actual IPC happens here:

IntRect WebPage::rootViewToScreen(const IntRect& rect)
{
    IntRect screenRect;
    sendSync(Messages::WebPageProxy::RootViewToScreen(rect), Messages::WebPageProxy::RootViewToScreen::Reply(screenRect));
    return screenRect;
}

This is showing up as idle stalls in DoYouEvenBench occasionally.
Comment 1 Darin Adler 2014-03-15 23:55:40 PDT
Should be pretty easy to reverse this so UI process sends the mapping to the web process.
Comment 2 Darin Adler 2014-03-16 01:07:24 PDT
Created attachment 226836 [details]
First cut
Comment 3 Build Bot 2014-03-16 01:57:30 PDT
Comment on attachment 226836 [details]
First cut

Attachment 226836 [details] did not pass mac-wk2-ews (mac-wk2):
Output: http://webkit-queues.appspot.com/results/5497521262559232

New failing tests:
platform/mac/accessibility/visible-position-crash-for-text-node.html
platform/mac/accessibility/text-marker-for-bounds.html
platform/mac/accessibility/range-for-position.html
platform/mac/accessibility/webkit-scrollarea-position.html
platform/mac/accessibility/scroll-to-visible-action.html
Comment 4 Build Bot 2014-03-16 01:57:31 PDT
Created attachment 226838 [details]
Archive of layout-test-results from webkit-ews-14 for mac-mountainlion-wk2

The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews.
Bot: webkit-ews-14  Port: mac-mountainlion-wk2  Platform: Mac OS X 10.8.5
Comment 5 Darin Adler 2016-10-19 10:27:00 PDT
The changes in bug 163648 are the practical solution to this problem.

*** This bug has been marked as a duplicate of bug 163648 ***