# Notification character bug

**URL:** <https://meta.discourse.org/t/notification-character-bug/128461>\
**Category:** UX\
**Created:** [September 13, 2019, 6:15am UTC](https://meta.discourse.org/t/notification-character-bug/128461 "2019-09-13T06:15:35Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![xrav3nz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/xrav3nz/32/76894_2.png) [@xrav3nz](https://meta.discourse.org/u/xrav3nz)\
**Post date:** [September 13, 2019, 2:18pm UTC](https://meta.discourse.org/t/notification-character-bug/128461/8 "2019-09-13T14:18:43Z")

</div>

Replying here so that others will have the context.

I thought this was weird because the notification tab does not share the same rendering codepath as the others, so I reverted the new quick access feature locally, and can still repro the issue:

 ![image](https://global.discourse-cdn.com/meta/original/3X/a/e/aef76ed9be9feb17885b34eb6acfaeb9fc75bfb0.png)

I believe this is a super edge case with our client-side `I18n.t`, and here is a minimal failing test for it: [https://github.com/xrav3nz/discourse/commit/3d7324281a285158fe75f9e7b42574906c940e49](https://github.com/xrav3nz/discourse/commit/3d7324281a285158fe75f9e7b42574906c940e49).

* * *

Fixed with:

[https://github.com/discourse/discourse/pull/8100](https://github.com/discourse/discourse/pull/8100)

---

_[View the full topic](https://meta.discourse.org/t/notification-character-bug/128461)._