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
@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)
@hirojin I mean, also yes
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