The "unread" dot in the Chrome tab icon is so small as to be almost invisible

[mvtglobally]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Open app and login in browser
2. From another account send couple messages
3. Check the "unread" indicator in the tab

Expected Result:

User should be able to see that there are unread messages

Actual Result:

User can see unread message indicator, but the The "unread" dot in the Chrome tab icon is so small as to be almost invisible

Workaround:

unknown

Platform:

Where is this issue occurring?

• Web

Version Number: 1.1.82-1
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1657511930574589

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @robertjchen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[robertjchen]

Yep, definitely not ideal! Wanted to loop in @Expensify/design on this: could we possibly get a mockup of what a new "unread" indicator would look like? It sounds like we might be changing it to a green color in addition to making it larger?

[melvin-bot]

Triggered auto assignment to @shawnborton (Design), see these Stack Overflow questions for more details.

[shawnborton]

Yup and perhaps we want to add some logic here:

• green is the default for unreads, etc
• show red when there is an error

Though I'm not sure if we have any red brick road logic just yet...

[shawnborton]

Posted an idea here

[robertjchen]

Looks great! We just need to swap out https://github.com/Expensify/App/blob/main/web/favicon-unread.png and we should be good to go here.

[parasharrajat]

Won't be that simple if we are looking to add two different ones based on error or non-error state.

[robertjchen]

Agreed- maybe we can just narrowly-scope this for just the unreads first. The error state would require some planning and discussion, especially since how the way we surface errors may be changing.

[shawnborton]

Let me know if these images work: Notification Dot.zip

[robertjchen]

It's beautiful, thanks!

[robertjchen]

Need to test things out before opening it up for review.

[robertjchen]

Update before going OOO: working through the test/screenshots checklist in the PR.

[shawnborton]

Not overdue