Non-standard usage? But still it's taking an advantages of WATIR,
b.element() is not completely equivalent to driver.find_element(), it does
the element_call so many things are taken care of!
On Thursday, October 26, 2017 at 5:20:12 AM UTC+5:30, Titus Fortner wrote:
>
> There are some good
>
> Instead of #click, what happens if you do #href instead? Do you see the
> difference in the results?
This comparison is no way related to what I am telling!
I am saying something which selenium has the capability to automatically
perform which we don't have to take care from our
> You realize you are effectively trying to 'mansplain' to one of the
> developers of Watir why not to use a majority of the Watir API? If you
> are just going to use b.element all the time, instead of making use of the
> Watir API and object model, then what is even the point of using
There are some good reasons to use watir 6+ even when not taking full advantage
of the location API. I'm behind on blogging all these things.
I just don't want to encourage non standard usage in our official mailing list.
--
--
Before posting, please read http://watir.com/support. In short:
On Wednesday, October 25, 2017 at 12:30:36 AM UTC-7,
rajagopalanmadas...@gmail.com wrote:
>
> Please reject my last mail, I was wrong about b.link(link_text:
> 'something').click
>
> Read this one, I have explained the advantage of link: over xpath:
> b.element(text: 'something').click
>
>
> It
Instead of #click, what happens if you do #href instead? Do you see the
difference in the results?
Regardless of whether you understand the reasoning, I'm asking that you not
tell Watir users to use the element method. If there is something that
can't be solved without the element method, then
I don't understand what you mean by " you don't care about the resulting
lack of encapsulation"? Care to explain?
What's wrong with telling the users the way it works? I am confusing
anything, I am pretty clear about what I talk
I am telling If they use
b.link(text: 'something').click
it
We actually had a long discussion at the Ruby test code hackathon in
Toronto last month about the proper behavior of the #text and #text_content
methods and how they relate to the text locator (which handles String and
RegExp values differently). I came into it arguing for changing the text
Please reject my last mail, I was wrong about b.link(link_text:
'something').click
Read this one, I have explained the advantage of link: over xpath:
b.element(text: 'something').click
It would create the selenium equivalent of
driver.find_element(xpath:
All the selenium locators are WATIR's locators as well, I don't have to use
element method if you don't like it, I could use link method as well with
b.link(link: 'something').click
it will still call selenium equivalent of
driver.find_element(link: 'something').click
no difference, but when
10 matches
Mail list logo
