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,
Hi Titus,
I am getting this warning while I execute this code
>
> @b.span(class: "spinner").wait_while(&:present?)
>
>
2018-09-05 12:26:45 WARN Watir [DEPRECATION] ["stale_present"] Checking
`#present? == false` to determine a stale element is deprecated. Use
`#stale? == true` instead.
If I
