Hi Daniel, I don't think that the maxlength value is intentionally ignored but rather than nobody thought to it.
I don't know what to think about it: on the one hand you're right, browser don't allow (without ruse) to set longer strings but on the other hand it is handy to test how the application reacts when the client side "protection" has be ignored... Marc. Daniel Brenner wrote: > Hi! > First the scenario: > I have a page containig an inputfield. The test should set the > inputfield with different values and then submits the value and checks > wether the value was succesful stored. The inputfield "contains" the > maxlenght attribute which limits the length of the input to a certain > value. In a browser (i.e. Firefox / IE) the input is limited to a String > with length <= maxlength. > Now the problem: > webtest allows to set the inputfield withs strings with length > > maxlength without making the setinputfield fail. Is the setinputfield > intended to work this way? > > Best regards, > Daniel > _______________________________________________ > WebTest mailing list > [email protected] > http://lists.canoo.com/mailman/listinfo/webtest > > _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
