Comments

• narayan Administrators

  January 2008

  Mikael, ideallly it should automatically wait. If it does not, then you could put a _wait(1000). If you could point us to a page, we can have a look at this problem.
• MultiMike Members

  January 2008

  Thanks for the quick answer.
  We actually got it to work now, so no need to use "wait". :-)
  
  /Mikael
• MultiMike Members

  January 2008

  I'm still a little worried about this issue.
  Today it appeared on a collegues computer also.
  
  Can you inform us how Sahi detects what scripts shall be injected into which page?
  Ie, how does it know when to wait after a command and when not to?
  
  /Mikael
• narayan Administrators

  January 2008 edited January 2008

  Sahi injects scripts into all pages which it thinks has html content.
  It will not inject the script into AJAX responses.
  
  Sahi waits if any part of the web page is loading. Be it a frame/iframe request or an AJAX request. But if the server takes a long time to respond on a non-AJAX call, and hence the current page is not unloading, then Sahi may go ahead and execute the next statement since it does not know that there is something that is yet to be loaded.
  
  Eg.
  
  Page1

  ---
  Link to Page2
  buttonA
  ---
  

  Page2

  ---
  buttonA
  ---
  

  And the script is

  _click(_link('Link to Page2'));
  _click(_button('buttonA'));
  

  If after executing _click(_link('Link to Page2'));, the server takes a long time to respond with Page2, the 'buttonA' of the first page may get clicked.
  So you may need to put an explicit wait in such a case.
  

  _click(_link('Link to Page2'));
  _wait(1000);
  _click(_button('buttonA'));
  

  Hope that helps.
• MultiMike Members

  February 2008

  Thanks for the explanation.
  
  Let's see if I got this right:
  1. A _click command is executed.
  2. Sahi waits a time (between every command)
  3. If a unload event is triggered, it waits for the new page.
  
  If this is the procedure, and the wait in step 2 is only ca 100ms, I guess it could be quite probable that the next command is executed to early?
  
  I think working around this with wait is unfortunate, because I would really like it to be deterministic,
  and it would be difficult to pinpoint all locations where the wait is needed.
  
  Is it possible to have a command that waits for a location to be loaded?
  For example:
  _waitLocation('http://localhost:8090/test.php');
  
  Or wait for a reload altogether:
  _waitReload();
  
  And the last question:
  Would it be safer if using items only accessible in the second page? for example:
  
  Page 1:

  Link to page 2
  Button1A
  

  and page 2:

  Button2A
  
• narayan Administrators

  February 2008

  There is a _wait(maxTime, condition);
  
  Have a look at http://sahi.co.in/w/_wait
  
  Yes, it is safer if using items only accessible in the second page.
• halluecehn Members

  April 2010

  Hi,
  
  I have a question similar to this, so I reuse this thread for it.
  
  How does sahi know when a web page is still loading and when it is fully loaded? What should be the condition to check for a page if it is fully loaded?
  
  Is there a possibility additionally to doing this check to reload the page after the timeout? The scenario here is the following: sometimes when a page shall be loaded, nothing happens, the browser 'hangs' forever with an empty page, but it might succeed to load the page if it reloads it.
  
  Best regards,