Jason,
Thanks for the tips. Indeed, this is a timing issue. I've tracked down
to the place where the last code made a click on the div and added
sleep 2 (sleep 1 not long enough, so I used sleep 2). It works totally
now.
Thanks again,
Winata
On Jun 7, 1:26 am, jason wrote:
> looks like you migh
looks like you might have a timing problem.
Try adding sleep(1) instead of puts to see if this is the case.
If this is the case you need to look at what you did before and if the
browser really did finish before it got to this line.
Jason
On 5 Jun., 23:33, Win wrote:
> Hi folks,
> I'm using c
