You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a post has a new comment, we show a blue mark on the number of comments the post has. We continue this UI/UX pattern by highlighting the new comments once we enter the comment section.
But nested comments are hidden behind a "view all n replies" so until we navigate to them we can't see any highlight.
I lived this moment of confusion searching the new comments everywhere only to then realize that the view all n replies number was growing
Screenshots
New comments on ItemInfo
View all n replies not highlighted
Steps To Reproduce
Click on a post that has new comments
Discover that there are no new comments highlighted
If you click on view all n replies, it finally shows the new comments highlighted.
Expected behavior
"view all n replies" should be highlighted as well, to indicate that there are new nested comments.
Logs
No response
Device information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Is there an existing issue for this?
Describe the bug
When a post has a new comment, we show a blue mark on the number of comments the post has. We continue this UI/UX pattern by highlighting the new comments once we enter the comment section.
But nested comments are hidden behind a "view all n replies" so until we navigate to them we can't see any highlight.
I lived this moment of confusion searching the new comments everywhere only to then realize that the
view all n replies
number was growingScreenshots
New comments on ItemInfo

View all n replies not highlighted

Steps To Reproduce
Expected behavior
"view all n replies" should be highlighted as well, to indicate that there are new nested comments.
Logs
No response
Device information
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: