Dierk Koenig wrote:
yes, but isn't that already covered by the word 'hidden'?

Possibly in this case it might be enough but then what to name:
forceClickButton if we wanted to allow users to click a disabled button
forceSetField if we wanted to allow the user to change a read-only field
etc.

Except that all other setXXX, clickXXX steps correspond to the user
clicking on a link, button, checkbox, or typing in some text, etc.
There is NOTHING that the user could ever do to force changing
the hidden field directly. Nothing to click, type, no menu option etc.

They can only do it indirectly when they eventually tricker some whacky JavaScript handler.

I see your point, though.

Hm, don't know. I'm too tired and need to go to the next session.

cheers
Mittie
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest



_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest

Reply via email to