title: Chrome warning "[DOM] Password forms should have (optionally hidden) username fields for accessibility" in console even with hidden username field
body: <p>When visiting the &quot;reset password&quot; route of my single-page app and looking at the Chrome browser console, I am greeted with the follwing warning:</p>
  <blockquote>
  <p>[DOM] Password forms should have (optionally hidden) username fields for accessibility: (More info: <a href="https://www.chromium.org/developers/design-documents/create-amazing-password-forms" rel="nofollow noreferrer">goo.gl/9p2vKq</a>)</p>
  </blockquote>
  <p>Helpfully, the html of the form in question is also printed to the console in the next line, and quite clearly <em>contains a hidden username field</em>:</p>
  <pre class="lang-html prettyprint-override"><code>&lt;form data-ember-action data-ember-action-436=​&quot;436&quot;&gt;​
    &lt;div class=​&quot;form-group&quot;&gt;
      &lt;label for=​&quot;newpasswordone&quot;&gt;​Password​&lt;/label&gt;​
      &lt;input type=​&quot;password&quot; autocomplete=​&quot;new-password&quot; placeholder=​&quot;Enter your new password&quot; id=​&quot;ember437&quot; class=​&quot;form-control ember-text-field ember-view&quot; data-op-id=​&quot;0&quot;&gt;​
      &lt;label for=​&quot;newpasswordtwo&quot;&gt;​Password (again)​&lt;/label&gt;
      ​&lt;input type=​&quot;password&quot; autocomplete=​&quot;new-password&quot; placeholder=​&quot;Re-enter your new password&quot; id=​&quot;ember438&quot; class=​&quot;form-control ember-text-field ember-view&quot; data-op-id=​&quot;1&quot;&gt;​
      &lt;input type=​&quot;hidden&quot; name=​&quot;username&quot; autocomplete=​&quot;username&quot; value=​&quot;a_b&quot;&gt;
    ​&lt;/div&gt;​
    &lt;button disabled type=​&quot;submit&quot; class=​&quot;btn btn-default&quot;&gt;​Reset password​&lt;/button&gt;​​
  &lt;/form&gt;​
  </code></pre>
  <p>I tried some minor variations -- unhiding the username field, marking it readonly, moving it outside the <code>div</code> -- without affecting the warning.
  How does Chrome expect to be served the username?</p>
  <p><em>Problem occurs with Chrome 63 and 64.</em></p>