[
http://jira.openqa.org/browse/WTR-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20046#action_20046
]
Alan Baird commented on WTR-466:
--------------------------------
I need to chime in here and say that the READYSTATE_INTERACTIVE saves me from a
really nasty hack dealing with these dialog boxes. When a script returns from
interacting with a save as dialog box, Watir still thinks it's in the wait
state. This makes it impossible to do any further automation because Watir is
stuck waiting on IE which will never get out of the wait state that Watir is
expecting.
I'm ok with not having it in there all the time as long as there is a decent
way to add this in during execution. It would be nice if it were in there all
the time so people that have to deal with save as dialog boxes wouldn't have to
wonder why it works that way until they stumble onto this issue. Maybe this
would be good to include in the FAQ - I will write this up if we decide to take
this out.
Don't hate us because we have to deal with the save as dialog box. :)
Alan
> 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
> Assignee: Bret Pettichord
> Priority: Major
> Fix For: Soon
>
>
> 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
Wtr-development@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-development
