evalJavaScript throws com.thoughtworks.selenium.SeleniumException

eda qa can do the fix from home, he s familiar with the problem.

Sent from my iPhone

On Aug 31, 2010, at 17:47, Oliver Raileanu <email address hidden> wrote:

> Public bug reported:
>
> Call of evalJavaScript 345.5; in a test unit shows the followng error:
>
> ####20100831174152:13:684aa38de33144398ceddde4a6cf2260:16886931:CMDDONE ( true )
> ####20100831174152:14:684aa38de33144398ceddde4a6cf2260:16886931:CMDINIT ( [getString, getEval, function evalAndEncode() { result = window.eval('345.5;');resultType = typeof result;return resultType + ':' + result;} evalAndEncode();] )
> ####20100831174152:15:684aa38de33144398ceddde4a6cf2260:16886931:CMDERROR ( [getString, getEval, function evalAndEncode() { result = window.eval('345.5;');resultType = typeof result;return resultType + ':' + result;} evalAndEncode();], com.thoughtworks.selenium.SeleniumException: ERROR: Threw an exception: function eval must be called directly, and not by way of a function of another name,
>
> ** Affects: testplan
> Importance: Undecided
> Status: New
>
> --
> evalJavaScript throws com.thoughtworks.selenium.SeleniumException
> https://bugs.launchpad.net/bugs/627479
> You received this bug notification because you are a member of TestPlan
> Team, which is subscribed to TestPlan.

This error has come back again it seems. To fix problems with Firefox I've upgraded Selenium in the package and will address this error with the newest selenium.

Fun, it appears that FireFox 3 specifically introduced such a limitation to be "standards compliant".

Nah, it appears that Selenium is breaking something, all the JavaScript code works correctly when run in the browser itself. Just have to figure out how it is breaking it now.

Try enough permutations of javascript and eventually it works. There is about a 10% chance this works with MSIE however...

Selenium-server has also been upgraded, main selenium not. This allows it to work with FireFox 3.5+.