Closed
Bug 44670
Opened 25 years ago
Closed 24 years ago
No correct IDLs for plugin XPCOM objects.
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
People
(Reporter: inn, Assigned: serhunt)
References
()
Details
Attachments
(2 files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
text/plain
|
Details |
For some plugins it required to have GUI Mozilla calls from other threads.
Common way to do that in Mozilla is interthread proxy (xpcom/proxy).
Usually those calls should be on nsIPluginInstancePeer interface, but this
mechanizm requires that target interface has XPT description (to generate proxy
object). I've made IDL, maybe it's enough. Also all other interfaces should be
IDLized.
___________________ nsIPluginInstancePeer.idl________________
#include "nsISupports.idl"
#include "nsIOutputStream.idl"
native nsPluginInstancePeerVariable(nsPluginInstancePeerVariable);
native nsPluginMode(nsPluginMode);
native nsMIMEType(nsMIMEType);
%{C++
#include "nsplugindefs.h"
%}
[scriptable, uuid(4b7cea20-019b-11d2-815b-006008119d7a)]
interface nsIPluginInstancePeer : nsISupports
{
[noscript] void GetValue(in nsPluginInstancePeerVariable variable,
// I know it's awful
in voidPtr value);
[noscript] nsMIMEType GetMIMEType();
[noscript] nsPluginMode GetMode();
[noscript] nsIOutputStream NewStream(in nsMIMEType type, in string target);
void ShowStatus(in string message);
void SetWindowSize(in PRUint32 width,
in PRUint32 height);
};
Reporter | ||
Comment 1•25 years ago
|
||
Reporter | ||
Comment 2•25 years ago
|
||
Comment 3•25 years ago
|
||
setting bug status to new. adding patch keyword
*** This bug has been marked as a duplicate of 39907 ***
Status: NEW → RESOLVED
Closed: 24 years ago
OS: Solaris → All
Hardware: PC → All
Resolution: --- → DUPLICATE
Comment 5•22 years ago
|
||
mass duplicate verifications . For filtering purposes, pls use keywd
"massdupverification"
Status: RESOLVED → VERIFIED
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•