-
Ok I get my patch.
I have updated the DialogWatcher.HandleWindow method by adding this check at the beginning of the method :
//If the window has not been launched by the process being tracked by this dialog watcher, do not handle it
if ( window.ParentHwnd != this._mainWindowHwnd )
return;
This seem to correct my problems.
2009-07-07 06:51:06 UTC in WatiN
-
Apparently when several IE instances are open simultaneously, the dialogs are not handled correctly.
Here is a simple page (no code behind) :
2009-07-06 15:04:51 UTC in WatiN
-
ok I got my workaround.
First I identify if my listbox will do a postback or not :
string onChange = this.select.GetAttributeValue("onchange");
bool willDoAutoPostback = onChange != null && onChange.Contains("PostBack");
This is only a hack but satisfying in my case for classical dropdownlist (and thus a call to __DoPostback or __WebFormDoPostbackWithOptions)
After that when...
2009-07-03 14:41:10 UTC in WatiN
-
I confirm my impression.
I am tracing the event BeforeNavigate2, AfterNavigate2 and DocumentComplete.
What happen in my case is that :
- I select the combo that does an autopostback
- I "WaitForComplete" --> it's complete
- I start selecting another combo
- The autopostback of the first combo starts
- BeforeNavigate2 is launched
- the selection of the second combo is being done -->...
2009-07-03 13:20:40 UTC in WatiN
-
I'm using WatiN-2.0.10.928-net-2.0
(And IE8)
2009-07-03 09:49:29 UTC in WatiN
-
I have created a very basic page (see in attachement for ASPX and code CS) with a dropdownlist that will do an autopostback. When I change the value, I will Thread.Sleep server side to simulate a long process.
See below my test :
using ( IE ie = new IE("http://localhost/AutoPostBack.aspx") )
{
ie.SelectList(Find.ById("cbo")).Select("Valeur 2");...
2009-07-03 09:35:06 UTC in WatiN
-
Hello,
while I was working with the FileUpload class, I have noticed that WatiN was very slow when typing full path name (that can be long, 100 characters in my case).
When investigating in the WatiN code, I have seen it was produced by the Hwnd.SendString method that was waiting for 50ms after each character, meaning 5 seconds in my case. Far too loong for my tests.
Can't these 50ms be...
2009-07-02 10:12:16 UTC in WatiN
-
Hello,
while I was working with the FileUpload class, I have noticed that WatiN was very slow when typing full path name (that can be long, 100 characters in my case).
When investigating in the WatiN code, I have seen it was produced by the Hwnd.SendString method that was waiting for 50ms after each character, meaning 5 seconds in my case. Far too loong for my tests.
Can't these 50ms be...
2009-07-02 09:28:31 UTC in WatiN
