# "You've notified but they can't see" message pops up too soon
**URL:** https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963
**Category:** Bug
**Created:** [8월 29, 2017, 12:21오전 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963 "2017-08-29T00:21:37Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@barryvan](https://meta.discourse.org/u/barryvan)
#### Post date: [8월 29, 2017, 12:21오전 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963/1 "2017-08-29T00:21:37Z")
When replying to a topic in a restricted category, Discourse (very intelligently) shows you a warning if you @-mention someone who won’t be able to see the topic. It does, however, seem to be a little eager in doing so. For example, if you type `@christine`, it’ll warn you that she can’t participate – even if you’re just about to finish typing `@christinejones`, who can.
I think this is tied to the autocomplete popup appearing – the warning banner appears at roughly the same time.
One way to fix this would be to not show this warning until you enter a terminating character – a piece of punctuation or whitespace.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [8월 29, 2017, 12:24오전 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963/2 "2017-08-29T00:24:56Z")
Yeah possibly, I have run into this as well. Any suggestions @cpradio?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [8월 29, 2017, 12:55오후 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963/3 "2017-08-29T12:55:12Z")
Agree, this happens to me regularly.
The simple fix fails though cause it would not show the warning when I type @barryvan
Maybe simplest is to bypass the check when “autocomplete” is open OR “autocomplete” was displayed in last 2 seconds.
---
### Author:  [@barryvan](https://meta.discourse.org/u/barryvan)
#### Post date: [8월 29, 2017, 1:38오후 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963/4 "2017-08-29T13:38:02Z")
Could a newline not be considered a terminating character? Although that still wouldn’t resolve people leaving trailing @-mentions at the end of posts. (Although you could argue that such people are truly, truly awful 😝!)
The autocomplete fix sounds like it could work well, but I imagine it’d be a bit more complex under the hood.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5월 15, 2018, 8:22오전 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963/5 "2018-05-15T08:22:37Z")
I believe you fixed this @sam?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [5월 15, 2018, 8:23오전 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963/6 "2018-05-15T08:23:44Z")
Yes this is fixed, there is a 2 second delay
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5월 22, 2018, 1:00오전 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963/7 "2018-05-22T01:00:09Z")
This topic was automatically closed after 6 days. New replies are no longer allowed.