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
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
Good news. I figured out how to minimize this message. Everything should be
better in 6.14. :)
On Tuesday, September 11, 2018 at 8:54:49 AM UTC-7, Titus Fortner wrote:
>
> The deprecation message is thrown when rescuing a stale exception during a
> call for #exists? / #visible? #present?
The deprecation message is thrown when rescuing a stale exception during a
call for #exists? / #visible? #present? because when we make the code
changes below, tests that rely on this behavior will fail. They need to
know about it, so there needs to be a message. Yes, the message is
happening
>
> element.wait_while(&:exists?)
No, this wouldn't work, I have to wait until the element is visible,
element becomes invisible when loading completes.
And also, I am checking whether element is visible or not, I am checking
whether previously located element exist in the DOM. So this line
This is another example of the deprecation notice being thrown more often
than it should be. I've verified that your code will work after my planned
deprecation. I can't figure out how to restrict this deprecation notice, so
I'll add something to the message.
Right now, to avoid that notice,
Yes I am asking the former, I need to wait until spinner goes away. So
former one is necessary for me. Buy why do you plan to deprecate such a
good method which is very much necessary?
On Wed 5 Sep, 2018, 8:06 PM Titus Fortner, wrote:
> It has to do with how Watir caches elements and being
Okay can you please let me know how can i replace the first line code of my
mine?
element=b.span()
element.wait_until(&:stale?)
Like this?
On Wed 5 Sep, 2018, 9:11 PM rajagopalan madasami, <
rajagopalanmadas...@gmail.com> wrote:
> Hi, I am creating log in y framework and this error message
Hi, I am creating log in y framework and this error message is troubling me
. There is a spinner comes and I need to wait until that spinner disappear
and my first line of code perfectly does the Job, why do want to deprecate
that method? I feel like you stared to deprecate all the necessary
It has to do with how Watir caches elements and being consistent in how it
responds.
"#present?" is asking "can a user see an element at this location?"
This is different from "did the element I previously located change?"
If you are asking the former, you're fine. If you are asking the latter,
10 matches
Mail list logo
