Just wanted to tell you, one more gem was released for page object, did you
check that out? Its watirpump.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
Hey Navi, I'm sorry there is so much confusion around the waits. If there
is something that would make this article
(http://watir.com/guides/waiting/) more clear, please let me know so I can
make it better. Maybe I spend too much time focusing on history and
implementation details that don't
You are perfectly correct, yes wait_while(&:exists?) will do the same Job, I
have not noticed when you explained me first time.thanks.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you
Yes I saw that in your article, that's best idea. Thanks.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before you ask, be nice.
watir-general@googlegroups.com
Hi Navi,
I don't think you'll be able to directly call Page-Object's #wait_for_ajax
from an after hook. You'll have to do the wait directly.
I believe you said you were using jQuery. Where you are initializing the
browser, add the following line to add the after_hook:
browser =
Hi Titus
Thats makes it very clear now :-)
Just to confirm, action methods as in set, click, select
And the reading attribute values like id, text, or any other custom
attribute are not auto covered and we need to use wait_until(&:present?)
Is that correct?
Cheers
Navi
On Tuesday, 11
Yeah, it is automatic only for action methods, which does not include text.
There's a case to be made to extend that behavior to text since it will
return an empty string if it isn't displayed, but for now you'll need to
keep the wait.
On Wed, Sep 12, 2018, 8:19 PM NaviHan wrote:
> Hi Titus
>
Hi Titus
Thanks for the detailed explanation and the documentation link.
Unfortunately my confusion doesnt get clarified.
As you said for an element which eventually displays, for example a pop up
that appears due to a user action, we can read the text by
*scenario 1*