Bug 146193

Summary: [Mac] MiniBrowser: The context menu on PluginView is displayed in the wrong position
Product: WebKit Reporter: Sungmann Cho <sungmann.cho>
Component: WebKit2Assignee: Sungmann Cho <sungmann.cho>
Status: NEW ---    
Severity: Normal CC: andersca, beidson, darin
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Screenshot of the issue
none
Patch beidson: review-, beidson: commit-queue-

Description Sungmann Cho 2015-06-21 07:54:57 PDT 
In order to calculate the exact position of the context menu on netscape plugins, the plugin instances need to know the size of the window frame in screen coordinates. This size is passed to NetscapePlugin::windowAndViewFramesChanged() from WebPageProxy::windowAndViewFramesChanged() and WebPageProxy::windowAndViewFramesChanged() gets the size from API::UIClient::windowFrame(), but the result is always 0 because there is no overridden implementation to return the actual size of the window frame.
Comment 1 Sungmann Cho 2015-06-21 08:06:21 PDT 
Created attachment 255324 [details]
Screenshot of the issue
Comment 2 Sungmann Cho 2015-06-21 08:09:17 PDT 
Created attachment 255325 [details]
Patch
Comment 3 Darin Adler 2015-06-23 12:08:56 PDT 
Any good way to make a regression test? Anders, does this seem like the right fix?
Comment 4 Sungmann Cho 2015-07-02 06:31:58 PDT 
Is there a regression test suite for testing MiniBrowser itself?
And I wanna know the patch is right.
Comment 5 Darin Adler 2015-07-02 09:38:21 PDT 
(In reply to comment #4)
> Is there a regression test suite for testing MiniBrowser itself?

No. But despite the bug title, this is not a bug in MiniBrowser.
Comment 6 Anders Carlsson 2015-07-02 10:49:45 PDT 
Need to double check what we do inside Safari and why there's even a UIDelegate client callback for this.
Comment 7 Brady Eidson 2017-04-24 19:11:30 PDT 
Comment on attachment 255325 [details]
Patch

This patch has been pending review since 2015 with no recent activity.
It seems unlikely that it would even still apply to trunk in its current form.

Clearing from the review queue.

Feel free to update and resubmit if the patch is still relevant.