Actually, ie.wait(true) would do the same thing.
Here is the code for Frame#wait:
def wait(no_sleep = false)
@container.wait(no_sleep)
end
It simply passes the wait call up to the container of the frame (the ie
object).
What wait does is wait for the page to
Just so you know, this doesn't do what you think: ie.frame(main).frame(sidebar).wait(analysisSidebarTabContent)It's actually the same as ie.frame(main).frame(sidebar).wait(true)
Hmm! So the statement I used is actually is checking to see
if the sidebar is there and NOT the
OK, thanks, Bret for the suggestion. Per your request, here
are some additional lines of code that preceded the while
statement.
There is the attach statement which may be
causing the problem since you had opened up a bug on that a couple of days ago?
ie.frame(:name,
Tx for the info.
Just so you know, this doesn't do what you think:
ie.frame(main).frame(sidebar).wait(analysisSidebarTabContent)
It's actually the same as
ie.frame(main).frame(sidebar).wait(true)
The fix regarding wait and attach is in 1.4., so this may be a new problem.
Bret
At 12:46 PM
The fact that you have to mess with all of this is probably a bug in the
wait method. Can you give us more info on what preceeds this code?
In the mean time, this should do what you want:
ie.frame(main).frame(sidebar).wait(analysisSidebarTabContent)
sleep 3
until (begin
