Summary: | Implement _NPN_SetException() correctly | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Cameron Zwarich (cpst) <zwarich> | ||||||
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED DUPLICATE | ||||||||
Severity: | Normal | ||||||||
Priority: | P2 | ||||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Attachments: |
|
Description
Cameron Zwarich (cpst)
2008-07-03 11:03:01 PDT
I think we could do something along the lines of the +[WebScriptObject setException:] API, which allows you to set an exception in the current execution context iff you're in a JavaScript callback to a plug-in interface. Created attachment 22078 [details]
Cleanup patch
Here's some some simple cleanup to make it easier to work on this code in the future.
Comment on attachment 22078 [details]
Cleanup patch
cpst and I discussed this over IRC. There is a behavior change bug in this patch. He's going to go for one more round of cleanup (and remove the added bug).
Created attachment 22089 [details]
Revised cleanup patch
Comment on attachment 22089 [details]
Revised cleanup patch
Looks fine.
Took me a minute to figure out what
_NPN_GetStringIdentifier
and
_NPN_GetStringIdentifiers were doing. I'm not sure the old argument names were very helpful, but the names of those functions certainly aren't.
Comment on attachment 22089 [details] Revised cleanup patch Cleanup patch landed in r35004. |