Bret, I've filed the issue in Jira as low priority. The ticket# is:
WTR-165
Thanks for your help.
-David
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
I've been using the development gem 1.5.1.1166 which includes the
re-written wait logic to test a complex SAP web application. The main
content that I am automating is nested 4 frames deep. Up until this
past Friday this version of watir seemed to handle waiting for all of
the inner frames to
Gems prior to 1.5.1.1166 would either give me the access denied errors
as it tried to wait for the inner frames to load - or if those were
suppressed, I had to put in a manual wait whenever I navigated to a new
page: sleep 0.1 until some_element_on_inner_frame.exists?. After
installing 1166 all
wait_until is a cleaner method to invoke. sleeps are too error prone,
wait_until a specific control exists. I removed the http error checks around
that time and there have been some changes in the frames handling.
-c
On 6/19/07, Brown, David [EMAIL PROTECTED] wrote:
Gems prior to 1.5.1.1166
Brown, David wrote:
Gems prior to 1.5.1.1166 would either give me the access denied errors
as it tried to wait for the inner frames to load - or if those were
suppressed, I had to put in a manual wait whenever I navigated to a new
page: sleep 0.1 until some_element_on_inner_frame.exists?.
