# Not confirming username autocomplete leads to confusing behavior

**URL:** <https://meta.discourse.org/t/not-confirming-username-autocomplete-leads-to-confusing-behavior/65228>\
**Category:** Bug\
**Created:** [6월 27, 2017, 8:41오후 UTC](https://meta.discourse.org/t/not-confirming-username-autocomplete-leads-to-confusing-behavior/65228 "2017-06-27T20:41:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)\
**Post date:** [6월 27, 2017, 8:41오후 UTC](https://meta.discourse.org/t/not-confirming-username-autocomplete-leads-to-confusing-behavior/65228/1 "2017-06-27T20:41:52Z")

</div>

This is not really a bug, but it is undesirable and counter-intuitive behavior.

We just had a customer that was pretty much panicking because it looked like users were seeing topics in the email digest that they shouldn’t see. It turned out that if the username autocomplete is not selected, the username is filled in into the username field, but is not being used.

This is not a single incident, in the past months we had at least five reports of strange behavior that could be pinned down to the administrator not confirming a username autocomplete. This time it was the digest preview, another incident involved adding users to a group.

Here is a screencap that shows what I mean. It involves user Richard who is a regular user, but who _seems_ to get a topic in an admin-only category in his preview digest.

> **[TechSmith Screencast](https://app.screencast.com/)**
>
> World's leading screen capture + recorder from Snagit + Screencast by Techsmith. Capture, edit and share professional-quality content seamlessly.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [6월 27, 2017, 11:23오후 UTC](https://meta.discourse.org/t/not-confirming-username-autocomplete-leads-to-confusing-behavior/65228/2 "2017-06-27T23:23:04Z")

</div>

Sure @eviltrout can you have a look? If it is generating lots of support requests we should try to address this.

---

<div class="post-metadata">

**Author:** ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)\
**Post date:** [6월 28, 2017, 7:39오후 UTC](https://meta.discourse.org/t/not-confirming-username-autocomplete-leads-to-confusing-behavior/65228/3 "2017-06-28T19:39:43Z")

</div>

I agree that is very confusing. I’ve punished my former self for implementing it so poorly and then created this:

[https://github.com/discourse/discourse/commit/f6222ff225c2d39c9db92e1b2de1249f5424d998](https://github.com/discourse/discourse/commit/f6222ff225c2d39c9db92e1b2de1249f5424d998)

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [7월 2, 2017, 1:00오전 UTC](https://meta.discourse.org/t/not-confirming-username-autocomplete-leads-to-confusing-behavior/65228/4 "2017-07-02T01:00:35Z")

</div>

This topic was automatically closed after 3 days. New replies are no longer allowed.