Re: [wtr-general] Re: This must be added into the recent Documentation in WATIR

Thank you Titus! On Monday, August 14, 2017 at 7:47:23 PM UTC+5:30, Titus Fortner wrote: > > That definitely needs to be updated. Watir 6+ makes the use of selenium's > implicit wait functionality completely unnecessary / actively bad for the > reasons you describe. > > > > On Aug 14, 2017 9:04

Re: [wtr-general] Re: This must be added into the recent Documentation in WATIR

That definitely needs to be updated. Watir 6+ makes the use of selenium's implicit wait functionality completely unnecessary / actively bad for the reasons you describe. On Aug 14, 2017 9:04 AM, wrote: And other thing I want to point it out here is implicit wait. Here you have talked about im

[wtr-general] Re: This must be added into the recent Documentation in WATIR

And other thing I want to point it out here is implicit wait. Here you have talked about implicit and explicit wait http://watir.com/docs/waiting/ You have mentioned about the implicit wait here, but this is not implicit wait at all for WATIR, WATIR has nothing to do with implicit wait, WATIR

Re: [wtr-general] Re: This must be added into the recent Documentation in WATIR

Ok that makes sense. On Aug 13, 2017 1:56 AM, "Titus Fortner" wrote: > I see what you are saying. Having an "under the hood" page. We could also > reference Alex's Watizzle implementation. > I don't think we'd want that on the main location page, because for most > people it matters the what of

[wtr-general] Re: This must be added into the recent Documentation in WATIR

I see what you are saying. Having an "under the hood" page. We could also reference Alex's Watizzle implementation. I don't think we'd want that on the main location page, because for most people it matters the what of the things you can do, not as much the how of its implementation. Also, for

[wtr-general] Re: This must be added into the recent Documentation in WATIR

> > I'm tentatively thinking about pulling in all of the html code we use in > our watirspecs onto the website, in order to have static pages to write > examples with. We could then copy and paste a lot of existing code in the > specs. Yes, that would be great! > On Saturday, August 12,

[wtr-general] Re: This must be added into the recent Documentation in WATIR

> > *"Yes, I have written about my desire for users not to need to know XPath > before: http://watir.com/watir-6-2/#adjacent-element-location > "* Yes, I have read that, but that doesn't detail much, I am talking about explaining what kin

[wtr-general] Re: This must be added into the recent Documentation in WATIR

Yes, I have written about my desire for users not to need to know XPath before: http://watir.com/watir-6-2/#adjacent-element-location That framing did not end up in the documentation updates I just made, but likely deserves to be added. Ideally that one page on element location gets split out in