RFE: Could the login page [0] get an HTML title element containing the string "Hacker News", say "Login | Hacker News"?<p>This would be immediately useful for password managers matching on window titles.<p>[0] https://news.ycombinator.com/login
> This would be immediately useful for password managers matching on window titles.<p>Password managers matching on window titles to decide what password to autofill sounds very dangerous! What password manager is this?
If they're going to update that page just add it to the list:<p>- Title (ideally unique, like Login | Hacker News)<p>- Use of section heading elements for "Login" and "Create Account"<p>- A background color<p>- Set the autocomplete attribute on the two password inputs to "current-password" for login and "new-password" for Create Account. Give both username inputs the autocomplete "username"[0]<p>- Give the two username and password inputs unique names (e.g. username, new-username, password, new-password)<p>- Stop being "clever" and change to standard HTML forms. Currently, both login/create forms point to the same endpoint, with the button's "value" mutating what that end-point does. This is completely non-standard and therefore difficult for any password manager to navigate without hard-coding. Instead, have each submit to a different endpoint (e.g. login, and create-account respectively).<p>- The forgotten password page also points to an endpoint called "x" and the username input has a different name than either one found on the login page "s" and no autocomplete hint.<p>If someone wanted to target HN with a bot, circumventing this would be trivial. It only really negatively impacts legitimate users trying to use password managers.<p>[0] <a href="https://developer.apple.com/documentation/security/password_autofill/enabling_password_autofill_on_an_html_input_element" rel="nofollow noreferrer">https://developer.apple.com/documentation/security/password_...</a>