-
Bug
-
Resolution: Fixed
-
P2
-
6
-
None
-
b53
-
generic
-
windows
-
Verified
Tested Build : JRE PIT and nightly build(build 1.6.0-b99) and promoted b-40
Build Location : /net/sqesvr-nfs.sfbay/global/nfs/deployment5/pit_builds
/net/koori/onestop/jdk/1.6.0/latest/bundles/
Problem description :
Noticed following inconsistencies across different browsers:
1) In the follwoing scenario mozilla/firefox doesn't throw any "javascript error messages" while there are proper error messages when invoked with IE
- <DeployeHelper>.install()
- <DeployeHelper>.launch()
- <DeployeHelper>.install(inavlid_no_of_args)
IE throws javascript error "Wrong no. of arguments" in all of the scenario mentioned above while mozilla/firefox does nothing(remains silent). If one tries to capture the return code then he/she can notice that "1"(means failure) is getting returned on mozilla/firefox in all the above mentioned invalid scenarios while in case of IE he/she won't be able to capture the return code. To maintain consistency either we should rely on return code or like IE should throw javascript error messages
2) This one is related to return code. On IE on execution of <DeployeHelper>.launch(JNLP_URL), return code is always "1" even though JAWS application is getting launched successfully without any errors/exceptions
3)This one is not related to consistency. In case of <DeployeHelper>.install(Invalid_JRE_BUNDLE_URL) "Error - getting Java(TM)" pop-up is coming up with a message "The bundel is either unsigned or corrupted". I think proper and valid message should be given to the user. Either we can have a different message or we can also extend the existing message to "bundel is either unsigned or corrupted or Invalid URL"
Steps to reproduce:
1) Install JRE from the location mentioned above
2) Load the following page inside your browser
http://sqeweb.sfbay.sun.com/deployment2/jitu/spec_improve_deploy/negative_tests1.html
If you notice behavior mentioned above while running the testcases then bug is reproduced
###@###.### 2005-06-17 20:22:07 GMT
Build Location : /net/sqesvr-nfs.sfbay/global/nfs/deployment5/pit_builds
/net/koori/onestop/jdk/1.6.0/latest/bundles/
Problem description :
Noticed following inconsistencies across different browsers:
1) In the follwoing scenario mozilla/firefox doesn't throw any "javascript error messages" while there are proper error messages when invoked with IE
- <DeployeHelper>.install()
- <DeployeHelper>.launch()
- <DeployeHelper>.install(inavlid_no_of_args)
IE throws javascript error "Wrong no. of arguments" in all of the scenario mentioned above while mozilla/firefox does nothing(remains silent). If one tries to capture the return code then he/she can notice that "1"(means failure) is getting returned on mozilla/firefox in all the above mentioned invalid scenarios while in case of IE he/she won't be able to capture the return code. To maintain consistency either we should rely on return code or like IE should throw javascript error messages
2) This one is related to return code. On IE on execution of <DeployeHelper>.launch(JNLP_URL), return code is always "1" even though JAWS application is getting launched successfully without any errors/exceptions
3)This one is not related to consistency. In case of <DeployeHelper>.install(Invalid_JRE_BUNDLE_URL) "Error - getting Java(TM)" pop-up is coming up with a message "The bundel is either unsigned or corrupted". I think proper and valid message should be given to the user. Either we can have a different message or we can also extend the existing message to "bundel is either unsigned or corrupted or Invalid URL"
Steps to reproduce:
1) Install JRE from the location mentioned above
2) Load the following page inside your browser
http://sqeweb.sfbay.sun.com/deployment2/jitu/spec_improve_deploy/negative_tests1.html
If you notice behavior mentioned above while running the testcases then bug is reproduced
###@###.### 2005-06-17 20:22:07 GMT