[ 
http://jira.openqa.org/browse/WTR-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20025#action_20025
 ] 

Jarmo Pertman commented on WTR-466:
-----------------------------------

The reason to include it was WTR-446. I'm using 1.6.7 at my workplace with 
tests running 24/7 and don't see this kind of issues. I'm wondering if there's 
something really specific which might cause that. It would be great if someone 
could make some reproducable case.

Also, what kind of an application are you using? Do you have frames? What kind 
of things fail? Are they related with JavaScript and/or Ajax?

Can you try with IE8 (maybe it's an older browsers problem, since i'm using 
IE8) and see if that happens then also?

Of course it would be also great if there's some ideas as to why browser won't 
be READYSTATE_COMPLETE as described in WTR-446 - maybe there's some better 
solution for that problem afterall?

> Issues to sync correctly with page load in watir1.6.7
> -----------------------------------------------------
>
>                 Key: WTR-466
>                 URL: http://jira.openqa.org/browse/WTR-466
>             Project: Watir
>          Issue Type: Bug
>          Components: Wait
>    Affects Versions: 1.6.7
>         Environment: Win XP IE6, IE7
>            Reporter: Aliaksandr
>            Priority: Major
>
> Hi, 
> We have recently updated our test environments to watir1.6.7 and our 
> scripts start to fail waiting for page to be fully loaded. Failures 
> happen when a script tries to access certain html elements on the page 
> while it is actually still loading. 
> We were able to figure out the cause of this behaviour. It is due to the 
> READYSTATE_INTERACTIVE state was added as the state to determine 
> browser load is complete: 
> ie-process.rb: 
> # Used internally to determine when IE has finished loading a page 
> READYSTATE_INTERACTIVE = 3 
> Wondering, what was the reason to include it? 
> This is an urgent issue for us (we have quite a few physical and virtual 
> client boxes for automation execution, which need a fix), so very appreciate 
> your help. For now we have to downgrade to watir1.6.5 throughout our test 
> environment.
> Best Regards,
> Alex

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.openqa.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development

Reply via email to