4 ms·

Yes, disabling autocomplete can be annoying, but it is possible. Usually it amounts to being more descriptive in the value of the `autocomplete` attribute, rath

Yes, disabling autocomplete can be annoying, but it is possible. Usually it amounts to being more descriptive in the value of the `autocomplete` attribute, rather than simply applying `autocomplete=off`. > We have observed Chrome showing a password prompt on an <input type=number> which is just bonkers. "We have observed" it, but not filed a bug? Neither of the bugs you linked to exhibit that bug.

crabmusket 2y ago
> Usually it amounts to being more descriptive in the value of the `autocomplete` attribute No, there are many inputs where there is no sensible autocomplete value. For example, "create a new CRM customer record". This is a new customer who I have not seen before. By definition it is impossible to autocomplete. In the past, the Chrome team advised to "make up an autocomplete value and we won't do anything with it". This advice is a) dumb and b) no longer works anyway. > but not filed a bug? It's clear the Chrome team has no interest in fixing this behaviour so I'm not going to waste my time. Yes, that's bad of me, but I have bills to pay.
- dfabulich 2y ago
  [flagged]
  - deleted 2y ago
    [deleted]
  - crabmusket 2y ago
    If you're a Chromium contributor or otherwise involved, I'd be happy to chat further about this and work up a submission to demonstrate the issue with a minimal repro. But if not, I don't think they need you to stick up for them. It's clear from the threads I did post that lots of devs are frustrated with Chrome's behaviour and the team's lack of attention to not just fixing bad behaviour, but complying with the HTML spec. Without even focusing on the type=number problem, I have spent enough time fighting other behaviour which is only an issue in Chrome. > you only vaguely remember a bug Thanks to that ad-hom I am now irritated, and I went back to our internal Slack to find the screenshot of the type=number bug. Sharing a screenshot here would have no real value to this discussion, but it's real.
  - schiem 2y ago
    A cursory search would show you how much frustration there is around broken autofill attributes. Such a dismissive attitude helps no one. Would you like me to paste the contents of the Jira issue I did last month working around a password input where we couldn't turn off autofill?
- exceptione 2y ago
  Chrome's slogan: "L'internet, C'est moi."
prmph 2y ago
Believe it or not, I have observed autocomplete behavior for an input change based on its label text.

crabmusket 2y ago

> Usually it amounts to being more descriptive in the value of the `autocomplete` attribute No, there are many inputs where there is no sensible autocomplete value. For example, "create a new CRM customer record". This is a new customer who I have not seen before. By definition it is impossible to autocomplete. In the past, the Chrome team advised to "make up an autocomplete value and we won't do anything with it". This advice is a) dumb and b) no longer works anyway. > but not filed a bug? It's clear the Chrome team has no interest in fixing this behaviour so I'm not going to waste my time. Yes, that's bad of me, but I have bills to pay.

dfabulich 2y ago
[flagged]
- deleted 2y ago
  [deleted]
- crabmusket 2y ago
  If you're a Chromium contributor or otherwise involved, I'd be happy to chat further about this and work up a submission to demonstrate the issue with a minimal repro. But if not, I don't think they need you to stick up for them. It's clear from the threads I did post that lots of devs are frustrated with Chrome's behaviour and the team's lack of attention to not just fixing bad behaviour, but complying with the HTML spec. Without even focusing on the type=number problem, I have spent enough time fighting other behaviour which is only an issue in Chrome. > you only vaguely remember a bug Thanks to that ad-hom I am now irritated, and I went back to our internal Slack to find the screenshot of the type=number bug. Sharing a screenshot here would have no real value to this discussion, but it's real.
- schiem 2y ago
  A cursory search would show you how much frustration there is around broken autofill attributes. Such a dismissive attitude helps no one. Would you like me to paste the contents of the Jira issue I did last month working around a password input where we couldn't turn off autofill?
exceptione 2y ago
Chrome's slogan: "L'internet, C'est moi."

prmph 2y ago

Believe it or not, I have observed autocomplete behavior for an input change based on its label text.