WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
12332
callWebScriptMethod:withArguments: provides no way to determine if an exception was thrown
https://bugs.webkit.org/show_bug.cgi?id=12332
Summary
callWebScriptMethod:withArguments: provides no way to determine if an excepti...
Mark Rowe (bdash)
Reported
2007-01-18 21:33:57 PST
As per the mailing list post in the specified URL, -[WebScriptObject callWebScriptMethod:withArguments:] translates an exception raised in the called method into a return value of WebUndefined. This makes it impossible to distinguish between a genuine return value of undefined and an exception being thrown. -[WebScriptObject callWebScriptMethod:withArguments:] returns nil in other situations: if the given method doesn't exist on the object, or if it is not a callable. It may make more sense to handle exceptions in a similar way, though the compatibility impact of changing the return value in this case is unknown.
Attachments
Add attachment
proposed patch, testcase, etc.
Mark Rowe (bdash)
Comment 1
2007-01-18 21:38:38 PST
<
rdar://problem/4941072
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug