History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: WTR-198
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Idan Miller
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Watir

Error in wait() method after clicking a link that loads a page and immidiately afterwards start another loading action

Created: 07/Feb/08 02:20 AM   Updated: 10/Jun/08 02:12 PM
Component/s: "Wait"
Affects Version/s: 1.5.3
Fix Version/s: 1.6.2

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Windows XP, ruby 1.8.6, watir 1.5.3


 Description  « Hide
This problem happens when I click a certain link, then the wait() method is
called behind the scenes.
So all I do is call the click method.

I get the following error:
 Caught NoMethodError: undefined method `times' for nil:NilClass
        C:/ruby/lib/ruby/gems/1.8/gems/watir-1.5.3/./watir/ie.rb:466:in `wait'

Following this discussion: http://groups.google.com/group/watir-general/browse_thread/thread/a985f895fd17fe34/772def964c32e67f?lnk=gst&q=Idan+Miller#772def964c32e67f
It was confirmed that this is a bug in watir having the wait returning nil for doc.frames.length.

I also noticed that after the click, a screen loads in the browser,
and then a loading of some other page is started.
I assume that because the wait() is called when the browser loads
another screen it somehow loses its reference to the frames?
I have no idea what is the problem here but that is all the info I
have...

Here is the link html, it calls javascripts so I don't really know
what's going on there.
<A class=topblong onclick=this.blur();
href='javascript:top.buildMenu("Investments", true)'>some text</A>

This is a blocker for me so if there is any manual patch that might solve this temoprarily before another version gets out please let me know.

Thanks,
Idan Miller.

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.