Did you use a password manager to pick your password?
I didn’t. I made my own password.
Are you able to reproduce the issue? If so what specific browser are you using?
Only in the case of manually initiating the “suggest me a password” scenario, though.
This does NOT happen with typical Chrome password saves. I guess that’s stronger evidence that it is a bug in Chrome, specific to this manually right-click initiated suggest step at the time of new account creation? 
Yes @riking updated the bug report to
Discourse forums broken by Chrome password generator
which definitely is correct in my testing.
Also note that this “suggest” option will not appear at all if you already have saved passwords for the domain. That makes it a pain to test, since you have to pick a Discourse at a domain you’ve never logged in to – or delete all your saved passwords for that domain.
I just created an account on this site, in Chrome, with zero issues whatsoever @sam.
I also logged out and logged in using the saved Chrome password with zero issues whatsoever.
So to be 100% clear, this bug is specific to “suggest password” in Chrome. At least if, like me, you run Chrome with stock defaults..
And also the “let chrome generate a password for you” popup box that only appears based on weird heuristics and disappears if you click in the wrong place and probably also experiment flags and also as a weird bar on mobile…
The right click is a reliable way of triggering the functionality, though.
What would you like done here? I am fairly confident I can drop the honeypot and replace it with a scheme that will be equally annoying to script kiddies
How can we quickly disable this mechanism for our site? This is the main question that worries me on the eve of the mass invitation of our partners. We could disable it until the official hotfix comes out.
P.S.: just as an idea, you could make the current algorithm optional
Nothing is necessary, per the repro the bug is in Chrome password suggestor. Best thing is for them to fix it.
Hello! I’m still wondering how we can disable this functionality right now?
You need a theme component, I recommend posting on Marketplace
Can you post instructions on how to disable this? I can make a plugin for it since we need to fix it on our instance. We are using Discourse as SSO provider and not letting our users register pretty much leaves them out of our whole infrastructure.
It doesn’t need to be a plugin.
I can write code to fix it, if that sounds better 
This is a very nasty issue, users are not able to sign up. There must be some fix 
I am afraid I am closing this for at least 3 more weeks to let Google have a chance at fixing this.
I hear that people are frustrated. @codinghorror’s call here is Chrome password generator is broken, Google should fix Chrome. Discourse is refusing to add a switch or setting for Discourse core unless we have actual customers that push us.
If you want to work around this it would be a 10 line theme component. Probably less.
That is … less letters than this actual post.
If you really want said theme component, post on Marketplace and I guarantee someone will build it. It would take me 15-20 minutes to build the component. Place a $2000 bounty on it I can guarantee someone will be keen to get $2000 an hour.
제가 직접 세팅한 사이트에서 이 문제가 발생하고 있어요. 아마추어라 제 실수인 줄 알았거든요.
제가 이해한 대로라면 이미 원인이 파악되었는데, 개발자가 10줄짜리 수정에 2천 달러를 요구하거나, 이 모호한 이슈에 대해 Google이 정책을 바꿀지 기다리는 수밖에 없는 상황이라고 합니다. 해결 가능성이나 예상 시기를 아는 분이 있을까요?
감사합니다.
저는 그렇게 이해하지 않았습니다. 그는 단순히 2,000달러를 제안하면 개발자가 구글 크롬 버그에 대한 임시 해결책을 빠르게 제공하도록 동기가 부여될 것이라고 말한 것뿐입니다. 하지만 아직 견적이나 추정치를 받기 위해 아무것도 제안한 사람이 없으며, 크라우드소싱을 시도해 본 사람도 없습니다.
Discourse 팀은 실제로 유료 고객들이 필요로 하지 않는 한 이 크롬 버그에 대한 임시 해결책을 제공할 계획이 없습니다. 따라서 이 옵션을 선택할 경우, 1년치 Discourse 호스팅 비용이 약 1,200달러(월 100달러)가 될 수 있습니다(교육, 비영리 및 오픈소스 사이트의 경우 가능한 할인 적용).
이 문제는 "비밀번호 제안"이 선택될 때만 발생합니다. 아마도 구상된 해결책은 테마 구성 요소를 사용하여 메뉴에서 해당 옵션을 제거하거나 숨기는 것일 수 있습니다.