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)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cjones, Assigned: jaas)

References

Details

(Keywords: dev-doc-complete)

Attachments

(1 file)

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.
And it prevents us from making any breaking changes to XPCOM.
Assignee: nobody → joshmoz
Version: unspecified → Trunk
Do we have any known consumers besides maybe the old OJI-based Java plugin and maybe Real Player?
Attached patch fix v1.0Splinter Review
Attachment #385314 - Flags: superreview?(jst)
Attachment #385314 - Flags: superreview?(jst)
Attachment #385314 - Flags: superreview+
Attachment #385314 - Flags: review+
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Blocks: 435431
Depends on: 510963
Depends on: 531290
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
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: