-
Enhancement
-
Resolution: Fixed
-
P3
-
6u10
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2198357 | 7 | Andy Herrick | P3 | Resolved | Fixed | b64 |
Error/exception messages should be across uniform different browsers and should be even considered while changing them when compared to pld Plug-in
Scenario I:
http://sqeweb.sfbay.sun.com/deployment2/jitu/plugInTestsNoHarness/Liveconnect/html/UserDefinedTest1.html
With old plug-in it used to throw same message across all browsers which is as follows:
netscape.javascript.JSException: No such method or property "textPrivate" on JavaScript object
But with new Plug-in on IE message is still the same but on FF3 it's throwing following message
netscape.javascript.JSException: JavaScript error: no such property "textPrivate"
ScenarioII:
Applet link:
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/ojiliveconnect/src/JSObjectRemMemb.html
A)
WIth old Plug-in we used to throw this message for members which cannot be removed using JSObject.removeMember API
"netscape.javascript.JSException: removeMember does not support <object name>"
With new Plug-in message has been changes to something like below
"netscape.javascript.JSException: Member <object_name> does not exist, or exists and can not be removed"
Is it Ok to change this message? 'Coz it's possible that users might consider it as a regression in a sense that outside world might be doing a check for "not supported exception" and trying to implement some kind of workaround.
Scenario I:
http://sqeweb.sfbay.sun.com/deployment2/jitu/plugInTestsNoHarness/Liveconnect/html/UserDefinedTest1.html
With old plug-in it used to throw same message across all browsers which is as follows:
netscape.javascript.JSException: No such method or property "textPrivate" on JavaScript object
But with new Plug-in on IE message is still the same but on FF3 it's throwing following message
netscape.javascript.JSException: JavaScript error: no such property "textPrivate"
ScenarioII:
Applet link:
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/ojiliveconnect/src/JSObjectRemMemb.html
A)
WIth old Plug-in we used to throw this message for members which cannot be removed using JSObject.removeMember API
"netscape.javascript.JSException: removeMember does not support <object name>"
With new Plug-in message has been changes to something like below
"netscape.javascript.JSException: Member <object_name> does not exist, or exists and can not be removed"
Is it Ok to change this message? 'Coz it's possible that users might consider it as a regression in a sense that outside world might be doing a check for "not supported exception" and trying to implement some kind of workaround.
- backported by
-
JDK-2198357 Plugin2: Uniform Liveconnect exception/error messages across all browsers
-
- Resolved
-