Official locator strategies for the webdriver : <p>In the <a href="https://w3c.github.io/webdriver/webdriver-spec.html#locator-strategies" rel="noreferrer">official W3c webdirver documentation</a>, it's clearly stated that the location strategies are:</p>

<pre><code>State   Keyword
CSS selector    "css selector"
Link text selector  "link text"
Partial link text selector  "partial link text"
Tag name    "tag name"
XPath selector  "xpath"
</code></pre>

<p>However, <a href="https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol" rel="noreferrer">Selenium's wire protocol</a> allowed:</p>

<pre><code>class name  
css selector
id  
name
link text
partial link text
tag name
xpath
</code></pre>

<p>In THEORY, Selenium's docs are obsolete and the "real" story is in the new spec document. However... </p>

<p>I ran some tests on the latest Chrome's own Webdriver, and I can confirm that <code>name</code> and <code>class name</code> both work; however, they are not in the specs.</p>

<p>I remember reading on a Chromium issue that they would only ever implement the official Webdriver specs.</p>

<p>Now: I <em>know</em> the generic answer, where "specs are not always followed 100%" etc. However, what I'd like to know is:</p>

<ul>
<li>Can you find the code in Chromium that implements this? (link would be most welcome)</li>
<li>Have there been discussions about these in the Chromium mailing list?</li>
<li>Are the "unofficial" commands (which are documented in the "old" selenium specs file) likely to stay? Where did you read so?</li>
</ul>
