Okay, I will wait until the next release, until then I use earlier version
of WATIR.
On Tue 4 Sep, 2018, 11:47 PM Titus Fortner, wrote:
> I mostly have the fix. There's some frame driver optimization that I
> realize is still needed.
>
> --
> --
> Before posting, please read
>
I mostly have the fix. There's some frame driver optimization that I realize is
still needed.
--
--
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.
you meant to say you have fixed it? Should I download any version of WATIR
to get the fix in my system?
On Tue, Sep 4, 2018 at 10:07 AM Titus Fortner
wrote:
> Well, now we're running into another bug that has to do with how element
> collections are located, which requires fixing the way
Well, now we're running into another bug that has to do with how element
collections are located, which requires fixing the way context is
established so that we can apply it to both elements and collections.
This should fix it:
https://github.com/watir/watir/pull/771
On Monday, September 3,
Titus, something really bad happened, now select list is not waiting for
element to exist, it immediately throws the error. Previous version works
fine. Something is missed.
On Mon 3 Sep, 2018, 11:49 AM Titus Fortner, wrote:
> Excellent! I'm glad it won't be a prohibitive change.
>
>
> On
Excellent! I'm glad it won't be a prohibitive change.
On Sunday, September 2, 2018 at 10:44:09 PM UTC-7, rajagopal...@gmail.com
wrote:
>
> Hi,
>
> I am sorry, It works fine. And you are absolutely right. Yes.
>
> b.element(visible_text: 'Sessions').click
>>
>
> Takes much time
>
> but
>
>
Hi,
I am sorry, It works fine. And you are absolutely right. Yes.
b.element(visible_text: 'Sessions').click
>
Takes much time
but
b.link(visible_text: 'Sessions').click
>
Takes very less time.
On Sunday, September 2, 2018 at 11:45:04 PM UTC+5:30,
rajagopal...@gmail.com wrote:
>
>
Sure, I will be in office tomorrow, so I will taking that element html and
posting it here.
I have posted a question in Stackover flow, can you please answer me there?
https://stackoverflow.com/questions/52130793/select-method-and-option-method-works-differently
On Friday, August 31, 2018 at
Can I see the html of the element you are trying to locate and the
locator you are trying to use?
On Thu, Aug 30, 2018 at 9:41 AM rajagopalan madasami
wrote:
>
> Hi, I have checked it, when I use visible_text its not even finding the
> element . Element not found error was thrown.
>
> On Thu 30
Hi, I have checked it, when I use visible_text its not even finding the
element . Element not found error was thrown.
On Thu 30 Aug, 2018, 4:59 AM Titus Fortner, wrote:
> Yes, Watir is only going to iterate over the link elements instead of all
> of the elements to find the matching text. If
Great info, thank you. I will try. I will try to use watigiri as well.
On Thu 30 Aug, 2018, 4:59 AM Titus Fortner, wrote:
> Yes, Watir is only going to iterate over the link elements instead of all
> of the elements to find the matching text. If there is a class or other
> attribute that would
Yes, Watir is only going to iterate over the link elements instead of all
of the elements to find the matching text. If there is a class or other
attribute that would further filter out links, that would help as well. It
will still be a little slower as there will be more wire calls, but I'm
Ah, okay , that makes difference? Okay let me check it today how it works.
On Thu 30 Aug, 2018, 4:12 AM Titus Fortner, wrote:
> Are you using element or link method?
>
> --
> --
> Before posting, please read
>
Are you using element or link method?
--
--
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
http://groups.google.com/group/watir-general
I tried using visible locator, its taking more than 5 seconds in some
places, but link locator clicks in no time.
On Thu 30 Aug, 2018, 3:32 AM Titus Fortner, wrote:
> You should be able to do a direct replacement with visible_text locator,
> just with the option of adding additional locators as
You should be able to do a direct replacement with visible_text locator, just
with the option of adding additional locators as desired.
--
--
Before posting, please read
https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group.
In short: search before
Hi Titus, please don't remove link locator from WATIR because many of our
project uses link locator in various places, so if you remove link locator,
we can't upgrade if new releases comes.
On Wed 29 Aug, 2018, 3:18 AM Titus Fortner, wrote:
> Based on my reading of the w3c spec, I think
Thank you.
On Wed 29 Aug, 2018, 3:18 AM Titus Fortner, wrote:
> Based on my reading of the w3c spec, I think IEDriver doesn't need to do
> this. The fix in Watir is easy enough, though:
> https://github.com/watir/watir/commit/84ca128739c1729bf8d8f46f92ae8a7c0ebfab0d
>
> It'll be in the next
Perfect! Thanks, Titus.
On Tuesday, August 28, 2018 at 2:48:21 PM UTC-7, Titus Fortner wrote:
>
> Based on my reading of the w3c spec, I think IEDriver doesn't need to do
> this. The fix in Watir is easy enough, though:
>
Based on my reading of the w3c spec, I think IEDriver doesn't need to do
this. The fix in Watir is easy enough,
though:
https://github.com/watir/watir/commit/84ca128739c1729bf8d8f46f92ae8a7c0ebfab0d
It'll be in the next release.
On Tuesday, August 28, 2018 at 11:02:58 AM UTC-7, rajagopalan
Thank you.
On Tue 28 Aug, 2018, 11:31 PM Titus Fortner, wrote:
> Interesting:
> https://github.com/SeleniumHQ/selenium/commit/406b8dab98ed7a06bbc35728fb2b061d068d9238
> I'll dig into what this is supposed to be doing so I can figure out the
> fix.
>
> On Monday, August 27, 2018 at 9:40:02 PM
Interesting:
https://github.com/SeleniumHQ/selenium/commit/406b8dab98ed7a06bbc35728fb2b061d068d9238
I'll dig into what this is supposed to be doing so I can figure out the fix.
On Monday, August 27, 2018 at 9:40:02 PM UTC-7, rajagopalan madasami wrote:
>
> Beautiful, thanks.
>
> On Tue 28 Aug,
Beautiful, thanks.
On Tue 28 Aug, 2018, 9:57 AM Lakshya Kapoor,
wrote:
> Yup, here is the source for Watir::Select#select:
>
> def select(*str_or_rx)
> results = str_or_rx.flatten.map { |v| select_by v}
> results.firstend
>
>
>
> On Monday, August 27, 2018 at 9:01:04 PM UTC-7, rajagopalan
Yup, here is the source for Watir::Select#select:
def select(*str_or_rx)
results = str_or_rx.flatten.map { |v| select_by v}
results.firstend
On Monday, August 27, 2018 at 9:01:04 PM UTC-7, rajagopalan madasami wrote:
>
> Ah ! Is it returning the value? I haven't noticed it so far. Let me
Ah ! Is it returning the value? I haven't noticed it so far. Let me verify.
On Tue 28 Aug, 2018, 9:29 AM Lakshya Kapoor,
wrote:
> I have experienced the same in IE. The exception is raised when
> Watir::SelectList#select attempts to read the selected value and return
> it while the page is
I have experienced the same in IE. The exception is raised when
Watir::SelectList#select attempts to read the selected value and return it
while the page is refreshing. My workaround was to use element.option(text:
myvalue).select and then read the value separately through element.text.
Should
Full Stack Trace
C:/Ruby/lib/ruby/gems/2.3.0/gems/selenium-webdriver-3.13.1/lib/selenium/webdriver/remote/response.rb:69:in
`assert_ok': Invalid internal element ID requested:
1981667e-660a-4b45-becf-98e2ebf7c71d
(Selenium::WebDriver::Error::NoSuchElementError)
from
27 matches
Mail list logo
