DescriptionFix nested GuestView's container bounds calculation.
This results in incorrect context menu positioning in pdf in webview or
webview inside appview.
If a guest A is nested within an embedder B, which in turn is nested inside
an embedder C, then we used to add offset twice to calculate the bounds of A
because BrowserPluginGuest::GetScreenCoordinates would add:
1. offset of C from A and
2. offset of B from A.
This CL removes step #2.
From logs, it seems to be there from the beginning of appview implementation.
BUG=507223
Test=Load a PDF inside <webview> and check context menu inside the PDF.
Easier to test with the browser sample:
https://github.com/GoogleChrome/chrome-app-samples/tree/master/samples/webview-samples/browser
You should observe the context menu is shown in the right place instead of
it being shifted.
Committed: https://crrev.com/87a98e428afa9dff6d02ff37d1504411d40fda3d
Cr-Commit-Position: refs/heads/master@{#339635}
Patch Set 1 #Patch Set 2 : clean up code a bit #Patch Set 3 : update and add test #Patch Set 4 : sync #Patch Set 5 : betterfix #
Total comments: 2
Patch Set 6 : pdf_extension_util -> pdf_extension_test_util #
Total comments: 2
Patch Set 7 : addres comments from raymes #Patch Set 8 : fix type mismatch for win_x64 compile #Messages
Total messages: 12 (3 generated)
|