|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)
- [JIRA] (JENKINS-15617) <st:bind> does... [email protected] (JIRA)

The idea behind geval is not to let evaluated script to access local in-scope variables as well as letting them put stuff into global scope, so I think it's sound to prefer geval as much as possible.
Now, it turns out execScript always return null which means it can't be used at all where we need the return value.
The next step is, who said eval on IE is broken? On my IE8 in the standards mode, "window.eval" seems to work as expected. MSDN backs me up and claims it has been there since IE6.