Skip to main content

Notifications disappearing on hover

  • March 27, 2025
  • 1 reply
  • 10 views

Teeg
  • New Participant
  • 8 replies

I have noticed some new behaviour in the ‘all notifications’ menu on the homepage which I find pretty concerning. If there are unread comments, as soon as one hovers over the comment window it automatically marks it as read. Both in the notifications menu AND in the file. This has proven detrimental as when just checking in on a comment, it clears! Often I do not respond to notifications in the notification menu from the homepage, and instead prefer to return to the actual file when I am working on that project, to see the comment properly and respond while looking at all the file’s context nearby. Now when I enter the file the comment bubble is marked as read and so it’s missed! This is terrible UX especially if one is busy merely scrolling through their notifications and now they’re all being marked as read. At least provide the user to turn off this ‘hover-to-mark-as-read’ feature.

See below example: After hovering over the first list item, it marks it as read. Just like that. Awful!

 

1 reply

  • Figmate
  • 1855 replies
  • March 28, 2025

Hi ​@Teeg, Thank you for bringing this to our attention!

 

I fully understand your concern. However, upon testing this on my end, I've observed that hovering over unread comments within the file browser notifications does not automatically mark them as read.

Specifically, after hovering:

  • The blue dot indicating unread status persists in the top right corner of the comment.
  • The comment continues to be listed in the “Unread” tab.
  • Upon opening the file, red dots are displayed on the Comment tool in the toolbar.

Furthermore, I have conducted an internal search but have been unable to locate any comparable reports.

 

We would appreciate further information to better understand the issue. Could you please verify the following?

  1. Is this happening in the browser, the desktop app, or both?
  2. Is this issue occurring with all comments, or is it specific to certain users or files?
  3. Are you experiencing the same behavior with other notifications, such as invitations or comment reactions?
  4. Have you tried any quick fixes to see if this behavior changes? 
  • Close any Figma tabs that you’re not using.  
    • For the browser: Force-quit your browser and reopen Figma in a new window. 
    • For the desktop app: Force-quit the Figma Desktop app and restart it.

If you're still having trouble after trying those quick fixes, please share a video of the issue. This will really help us get you connected with the right team if we need to escalate it.

Thanks again for reaching out!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings