Summary
The homepage login password field does not declare an autocomplete value. Chromium warns about the missing attribute, and password managers must guess whether the field represents an existing credential, a new password, or a one-time value.
Current markup:
<input autofocus maxlength="9" name="uid" placeholder="Your Password" required size="13" type="password">
Steps to reproduce
-
Open https://apn.tech/ in Chromium.
-
Open the browser developer console.
-
Observe the DOM warning:
Input elements should have autocomplete attributes
-
Inspect the input[name="uid"] element.
-
Observe that it has type="password" but no autocomplete attribute.
Actual result
The browser receives no explicit credential-purpose hint and emits a warning. Password managers and autofill implementations must infer the field's purpose from a single-field form.
Expected result
Declare the intended autocomplete token explicitly. Because the form is labeled Login and accepts an existing APN credential, autocomplete="current-password" appears appropriate. If the product considers this a generated/new credential instead, use the corresponding standards-compliant token intentionally.
Impact
APN says its password is generated on-device and is the only credential used for web login. Reliable password-manager recognition is therefore particularly useful; missing semantics can make saving and filling that credential inconsistent across browsers and assistive tooling.
Duplicate check
Searched open and closed issues for autocomplete, password manager, current-password, new-password, and the homepage password markup.
Nearby issues are different:
No existing report covers this browser warning or autocomplete behavior.
Environment
Observed on 20 August 2026 on the production homepage using Chromium 152 at desktop and mobile viewport sizes. No credential was entered and no login request was submitted.
Summary
The homepage login password field does not declare an
autocompletevalue. Chromium warns about the missing attribute, and password managers must guess whether the field represents an existing credential, a new password, or a one-time value.Current markup:
Steps to reproduce
Open https://apn.tech/ in Chromium.
Open the browser developer console.
Observe the DOM warning:
Inspect the
input[name="uid"]element.Observe that it has
type="password"but noautocompleteattribute.Actual result
The browser receives no explicit credential-purpose hint and emits a warning. Password managers and autofill implementations must infer the field's purpose from a single-field form.
Expected result
Declare the intended autocomplete token explicitly. Because the form is labeled Login and accepts an existing APN credential,
autocomplete="current-password"appears appropriate. If the product considers this a generated/new credential instead, use the corresponding standards-compliant token intentionally.Impact
APN says its password is generated on-device and is the only credential used for web login. Reliable password-manager recognition is therefore particularly useful; missing semantics can make saving and filling that credential inconsistent across browsers and assistive tooling.
Duplicate check
Searched open and closed issues for
autocomplete,password manager,current-password,new-password, and the homepage password markup.Nearby issues are different:
type="text"and exposed characters. That is fixed; the field now usestype="password".autocompleteattribute.No existing report covers this browser warning or autocomplete behavior.
Environment
Observed on 20 August 2026 on the production homepage using Chromium 152 at desktop and mobile viewport sizes. No credential was entered and no login request was submitted.