Hello everyone,
I'm noticing a strange behaviour when my Win32 Fx 3.6.6 (JSSH 0.9,
Ruby 1.8.6, [Fire]Watir 1.6.5) loads a page and it winds up being
pulled from cache: Firewatir doesn't wait for the page to load, at
all. It immediately fires, often on a non-existent or still-rendering
page/DOM.
Is this a known problem? Is there a workaround? (either via browser
settings or a Firewatir setting?) Since wait() is not doing anything
in these situations, I don't want to have to start sprinkling
Watir::Waiter::wait_for { } blocks in the hundreds of spots this would
be potentially required in my test suite. Watir::IE handles
everything I throw at it just fine.
It's difficult to post code when working in a proprietary house, if
requested I'll try to create a reproducible scenario based on what I'm
seeing.
- Rob
--
Before posting, please read http://watir.com/support. In short: search before
you ask, be nice.
You received this message because you are subscribed to
http://groups.google.com/group/watir-general
To post: [email protected]
To unsubscribe: [email protected]
