- From: John Jansen <John.Jansen@microsoft.com>
- Date: Wed, 10 Jun 2015 22:57:34 +0000
- To: Jim Evans <james.h.evans.jr@gmail.com>
- CC: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
> 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 >
Received on Wednesday, 10 June 2015 22:58:12 UTC