Have you noticed any problem for waitForPageToLoad in the bundle? As long as the waitForPageToLoad command was pushed to Engine at the time when it was called, it would be fine. But if waitForPageToLoad is queued up with other commands, we may have a problem. Tellurium core is designed to issue the waitForPageToLoad command immediately with all other commands in the queue when it receives the call.
The waitForCondition has to be called in its original format because Selenium RC needs to do some work for it. waitForPageToLoad may not be the case. Thanks, Jian On Fri, Mar 5, 2010 at 6:23 AM, dominicm <[email protected]> wrote: > Hi, > > It seems that waitForPageToLoad has found it's way into a bundle: > > info(1267786595541): Executing: |getBundleResponse | [{"uid":"","args": > ["30000"],"name":"waitForPageToLoad","sequ":43}] | | > > Shouldn't this be executed directly similar to waitforCondition as > below? > > info(1267786591716): Executing: |waitForCondition | try {var doc = > selenium.browserbot.getCurrentWindow(true).document;doc.readyState == > 'complete'}catch(err){false} | 15000 > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "tellurium-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<tellurium-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/tellurium-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=en.
