Closed Bug 53507 Opened 25 years ago Closed 23 years ago

nsIPluginInstance::SetWindow hides xwindow handle

Categories

(Core Graveyard :: Plug-ins, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.0.1

People

(Reporter: s.schaefer, Assigned: rubydoo123)

Details

(Keywords: arch, Whiteboard: [documentation])

The structure passed to a plugin by nsIPluginInstance::SetWindow does not contain a valid xwindow handle (UNIX). Instead the window member of the passed nsPluginWindow points to a "GdkSuperWin" object which contains a "GdkWindow" (bin_window) which holds the required xwindow handle to the plugin window. At least this should be documented, but then it requires using internal Mozilla structures in the plug-in code which should be avoided.
marking new and cc-ing architecture weenies
Status: UNCONFIRMED → NEW
Ever confirmed: true
Moving to m1.0 and reassigning to peterl.
Assignee: av → peterl
Target Milestone: --- → mozilla1.0
Is this an envangelism issue or is there a problem in our implementation? Have you read the new plugin API guide under Developer Docs on mozilla.org? Nominating WONTFIX
Status: NEW → ASSIGNED
---> envangelism
Assignee: peterl → evangelism
Status: ASSIGNED → NEW
Component: Plug-ins → Evangelism
QA Contact: shrir → zach
Reassigning evangelism bugs to bclary@netscape.com.
Assignee: evangelism → bclary
Arun, I'm giving you all the Linux bugs. If these bugs can be confirmed for other OS's please (someone) change the Platform/OS to All/All and reassign to the default Evangelism Component Owner.
Assignee: bclary → aruner
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Target Milestone: mozilla1.0 → ---
Version: other → unspecified
Arun, I am taking your Linux bugs minus banks. Hope you don't mind.
Assignee: aruner → bclary
back to Arun for plugin bugs
Assignee: bclary → aruner
-> Plugins
Component: US General → Plugins
QA Contact: zach → mgalli
Frankly, I'm confused. What exactly is the evangelism issue? Can someone step in and clarify?
back to browser plugins. If you guys feel your documentation is good enough (it isn't) then you may reasign this bug to the doucmentation product for them to rewrite it. IMO your documentation isn't clear at all, I can't even follow lxr pointers (idl and header only) to find out that it's a gdk*.
Assignee: aruner → av
Component: Plugins → Plug-ins
Keywords: arch, mozilla0.9.9
Product: Tech Evangelism → Browser
QA Contact: mgalli → shrir
Version: unspecified → other
-->serge
Assignee: av → serge
I have asked Ian to make sure this gets addressed in the updated referene manual.
Assignee: serge → beppe
Whiteboard: [documentation]
Target Milestone: --- → mozilla1.0.1
Yes. I will put something in the docs about this. In fact, I'll write something up and post it here to make sure I've got it right, then I'll go into the plug-in guide about it.
I've added this to the notes for NPP_SetWindow. It's nearly verbatim from s.schaefer's first comment here: "On Unix, the structure passed by NPP_SetWindow does not contain a valid xwindow handle. Instead the window member points to a "GdkSuperWin" object, which contains a "GdkWindow" (bin_window), which in turn holds the required xwindow handle to the plugin window." Does this suffice?
I don't understand what's this bug about. yes at the beginning of ns4xPluginInstance::SetWindow(nsPluginWindow* window) window->window is not a valid xwindow handle, but we assign it later http://lxr.mozilla.org/mozilla/source/modules/plugin/base/src/ns4xPluginInstance .cpp#896 so on Unix, the structure passed to NPP_SetWindow *DOES* contain a valid xwindow. Why we should docummented nsIPluginInstance::SetWindow() call?
The bug description stems back from the Mozilla Milestone M18 or something. Meanwhile the problem is gone and the correct structures are passed to the plugin. No further action required.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
based on user comment, marking as verified
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.