Confirming to bring to developer's attention. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
Although this is true, there is a workaround that plugin developers can use. As an example, if a plugin has a stop method, stop should be replaced with another identifier like stopPlugin. Then the plugin needs to implement nsIXPCScriptable and use nsIXPCScriptable::Create to dynamically generate a js prototype that redirects the 'stop' call in html content to the native 'stopPlugin' call. see http://lxr.mozilla.org/seamonkey/source/js/src/xpconnect/tests/components/xpctes t_overloaded.cpp for an example of a component that does something similar.
firstname.lastname@example.org - does this response answer your question? Can this bug be closed? Gerv
If the plugin API is frozen, then this could be closed as WONTFIX. Otherwise, it would be nice if Start and Stop were renamed something like npStart and npStop.
This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug,or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.
Target Milestone: --- → Future
If the bug won't be addressed before the plugin API interface freezes, then it should not be marked FUTURE. This should be addressed either as part of the API freeze or marked as WONTFIX.
The API is frozen--->WONTFIX
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.