[
http://jira.openqa.org/browse/WTR-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20036#action_20036
]
Jarmo Pertman commented on WTR-466:
-----------------------------------
Still looking? Did you find anything? I've had some thoughts about that issue
and it seems to me that it's best to make it work as it was before - e.g. only
waiting for READYSTATE_COMPLETE. But to satisfy the WTR-446 the waiting states
ought to be modifiable - maybe introducing some constant as an Array which by
default has only READYSTATE_COMPLETE in it and for WTR-446 it's just possible
to add READYSTATE_INTERACTIVE to the array and remove it afterwards. That would
make #wait work as it was before and also allowing to use some workarounds for
browser quirks.
I'm gonna implement it soonish.
> 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
>
> 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
