# Impossible to read some notifications when using Legacy navigation

**URL:** <https://meta.discourse.org/t/impossible-to-read-some-notifications-when-using-legacy-navigation/257511>\
**Category:** Bug\
**Created:** [March 8, 2023, 4:57pm UTC](https://meta.discourse.org/t/impossible-to-read-some-notifications-when-using-legacy-navigation/257511 "2023-03-08T16:57:44Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![mentalstring](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mentalstring/32/168934_2.png) [@mentalstring](https://meta.discourse.org/u/mentalstring)\
**Post date:** [March 10, 2023, 3:23pm UTC](https://meta.discourse.org/t/impossible-to-read-some-notifications-when-using-legacy-navigation/257511/12 "2023-03-10T15:23:08Z")

</div>

I have tested this and confirm that the dismiss button clears the unreadable notifications.

That said, we are bound to confuse already frustrated users as they might click the notification (the mention) before using the Dismiss button, either because they haven’t read our instructions yet on why were mentioned, or just because they need some handholding.

Well, at least there’s a workaround: some users have accumulated quite a few of these and will be happy to have that reset. We’ll be upgrading to 3.0 tomorrow and we’ll try to help them afterwards.

---

_[View the full topic](https://meta.discourse.org/t/impossible-to-read-some-notifications-when-using-legacy-navigation/257511)._