Hi Patrick,
I noticed my tests would navigate to the page but would hang during the setValue command. Does scripting work for Chrome Frame?
Thanks!
Some scripting works but anything that needs to interact with the DOM does not (we don’t have access into the Chrome Frame DOM running inside of the IE container).
Is there a workaround to running scripted tests where it requires us to put in a username and password into input fields? Will DOM interaction with Chrome Frame be supported in the future?
It’s unlikely that DOM interaction will be supported any time soon. If you are testing an authenticated page your best bet would be to log in on a desktop, grab the session cookie for your session and use the setCookie command to have the test agent re-use your session (assuming they are not locked down to IP address). The cookie commands should work fine since Chrome Frame uses IE’s networking stack.