Re: Element location strategies

We agreed that the rest were superfluous to our needs.

I have an initial implementation in a client binding at
https://github.com/AutomatedTester/selenium/blob/wires/py/selenium/webdriver/remote/webdriver.py#L656

David

On 10 June 2015 at 23:57, John Jansen <John.Jansen@microsoft.com> wrote:

> > I believe the general consensus was that the language bindings could
> easily translate those locator strategies into simple CSS selectors. So
> while the client-facing API would remain the same for > compatibility's
> sake, the remote end only had to understand finding by CSS selectors. But
> I'm old, and my memory isn't what it used to be.
>
> That definitely makes sense to me. I just wanted to verify that's the
> decision we made.
>
>
> > On Jun 10, 2015, at 18:04, John Jansen <John.Jansen@microsoft.com>
> wrote:
> >
> > In reading through the spec for Element Location Strategies[1], I cannot
> help but notice a few strategies are missing. I looked through some minutes
> from our face-to-face meetings, and I cannot find notes on them. It's
> likely I didn't search hard enough.
> >
> > Missing:
> > By.tagName()
> > By.className()
> > By.Name()
> >
> > Were they left out on purpose?
> >
> > [1]
> https://w3c.github.io/webdriver/webdriver-spec.html#element-location-strategies-1
> >
>
>