Closed
Bug 500513
Opened 16 years ago
Closed 16 years ago
Stop allowing plugins to access XPCOM through NPN_GetValue()
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cjones, Assigned: jaas)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
|
1.82 KB,
patch
|
jst
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
Plugins can call NPN_GetValue() with the values NPNVserviceManager, NPNVDOMElement, or NPNVDOMWindow and get pointers to XPCOM instances. They should not be able to do this.
Among other reasons that this interface is troublesome is that it will extremely painful to impossible for us to support when plugins run in separate processes.
Comment 1•16 years ago
|
||
And it prevents us from making any breaking changes to XPCOM.
Do we have any known consumers besides maybe the old OJI-based Java plugin and maybe Real Player?
Attachment #385314 -
Flags: superreview?(jst)
Updated•16 years ago
|
Attachment #385314 -
Flags: superreview?(jst)
Attachment #385314 -
Flags: superreview+
Attachment #385314 -
Flags: review+
pushed to mozilla-central
http://hg.mozilla.org/mozilla-central/rev/7b55c4e84bcb
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Depends on: 503902
Comment 8•16 years ago
|
||
Should we update https://developer.mozilla.org/en/NPN_GetValue
to mention that getting these values is deprecated in Firefox 3.6?
Keywords: dev-doc-needed
Comment 9•16 years ago
|
||
Documentation updated:
https://developer.mozilla.org/en/NPN_GetValue
Also mentioned on:
https://developer.mozilla.org/en/Firefox_3.6_for_developers#Miscellaneous
Keywords: dev-doc-needed → dev-doc-complete
Depends on: 545224
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•