a weird omission is that every browser has built-in autofill now with all sorts of label/name heuristics to figure out what forms represent, but none of them have any inspector features to check how a form is actually perceived by the browser’s autofill implementation

“why don’t you recognise that this is an email field” is a question Chrome’s inspector should absolutely be able to answer

this is only exacerbated by the fact that most search results for “[browser] autocomplete attributes” returns stack overflows of people foolishly trying to *circumvent* browser autofill features, not expressly enable them

@hirojin absolutely definitely developers (probably working for banks or other institutions who want to make login forms as obtuse as possible because they’ve been fed security FUD)

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!