[
http://jira.openqa.org/browse/WTR-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20042#action_20042
]
Jarmo Pertman commented on WTR-466:
-----------------------------------
I think that it's better to have by default only READYSTATE_COMPLETE as it has
been for "centuries" than to cause occasional problems here and there. It would
be great to know why and where these problems occur of course, until then i
would prefer reverting #wait to use READYSTATE_COMPLETE only.
It makes even more sense when you think that the "save as" dialog problem is a
really specific one and only one situation where browser seems to behave
strangely currently.
So, instead of fixing only very specific problem and causing n-count of unknown
problems i'd prefer the latter.
It is really easy to add that missing READYSTATE_INTERACTIVE when dealing with
"save as" dialogs:
{noformat}
def some_method
Watir::READYSTATES[:interactive] = 3
# do something with save as dialog
ensure
Watir::READYSTATES.delete(:interactive)
end
{noformat}
> 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
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development
