Closed Bug 673054 Opened 13 years ago Closed 8 years ago

Better error reporting in NPAPI

Categories

(Core Graveyard :: Plug-ins, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: malek, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110628 Ubuntu/10.10 (maverick) Firefox/3.6.18 Build ID: 20110628231248 Expected results: Following up on bug 670629, it would be useful if plugins could report errors back to the user.
Proposal 1 - Use the console service: NPN_Report(const char *message, uint32_t flags, const char *sourceName, uint32_t lineNumber) (This could also accept a sourceLine and columnNumber params to draw an arrow in the error console, but I don't really see the point.) This would create nsIScriptError objects and log them to the console. Proposal 2 - Use the JSAPI: NPN_Report(const char *message, uint32_t flags) This would use JS_ReportError or JS_ReportWarning depending on the flags value. (I didn't propose a format + variable argument list because I don't think a va_list would cross the ipc boundaries.) Any feedback/suggestions/other proposals are welcome. P.S.: I can give a try implementing any of these proposals (In fact I already did proposal 1), but I'need a little bit of help.
the test is not quite good because I don't know how to avoid the enablePrivilege issue. (I'm sure there are other problems...)
OS: Other → All
Flash is the only NPAPI now, and is considered legacy, so we're not going to implement further improvements.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
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: