We have been seeing this issue where WatiN will throw a
WatiN.Core.Exceptions.TimeoutException after highlighting the element and
then just sitting there. It is not consistently failing, but fails often
enough to throw off accurate test results. It seems limited to textfield
I have tried setText on the textfield, and that seems to work. However, I
would prefer to use .type.
For the selectlist, it doesn't matter if I select by index, value, text,
etc, it will highlight and then just sit there.
The difference is that the selectlist will actually choose the item, then
timeout. Whereas the textfield will never type.
I am able to catch the timeoutexception and give it another try, however,
usually if it fails the first time, it will the second time (even if I force
a page refresh). I looked through the WatiN code and noticed that after it
selects the item from the select list, it fires the onChange event. So, I
mimicked that and it only seem to help a little bit.
Has anyone seen this happen before?
WatiN version: 2.0 Beta 1
IE version: IE 7