I did make a rather bold statement in an other topic on javascript support
in Webtest. Reactions on this statement seem to indicate that I must be
missing something, so I'll try to explain here why I made this statement.
I have an HTML page with a form that goes like this:
...
<select id="niveauCode" name="niveauCode"
onchange="javascript:submitForm('etudeForm','refresh');">
<option value="invalid">Sélectionnez une valeur</option>
<option value="AP">More options...</option>
</select>
... more html here
The onchange javascript goes like this:
...
function submitForm(formId, eventName){
document.getElementById(formId)._eventId.value = eventName;
document.getElementById(formId).submit();
}
... A classic javascript that will submit the page in order to update the
next select lists in the form.
Using a setSelectField I do not get the same behaviour ( that is, a new page
with updated selects) as when I use an equivalent invoke... so, using the
setSelectField I get an error page while using the invoke I get my updated
page and can continue testing...
So I'd like to have your opinion on wether this a javascript issue or not?
TIA
--
View this message in context:
http://www.nabble.com/javascript-issue-or-not--tp19512515p19512515.html
Sent from the WebTest mailing list archive at Nabble.com.
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
