Comment disappears on specific comment formats

Hey Darshana, thanks for flagging this and sharing the screenshots, that's helpful to visualise the issue. I tried reproducing this on my end with the same formatted comment (bold heading + nested bullets) and it saved correctly, so this may be intermittent rather than a general issue affecting everyone.

As a workaround in the meantime, before saving a formatted comment, it may help to copy the text elsewhere just in case, so nothing is lost if it happens again.

If this keeps happening, please submit a bug report through the Support Hub: Support Hub → type "Report a bug, Contact an agent" → Click "Start a chat", follow the prompts. In the form, please include:

• The URL of the affected file, with Can View access granted to support-share@figma.com
• The screenshots you shared here
• A screen recording of the formatting loss happening, if possible
• Whether this has happened in other files/comments, or only this one

This will help our team reproduce the issue on your specific file and investigate further. Thank you!

I am having the same problem, FYI.

Client attempted to use bullet points, the bullet point content was erased.

• Email notification showed the intro with one blank bullet, followed by two more bullets with content. Oddly it was the content for the first bullet is what had been deleted by the system.
• Figma file itself only shows the blank bullet, then nothing else.
• Client was temporarily able to see the full comment on her end even while we were not, but then could only get the deleted version after a short time

Is this solely due to the bullet-point formatting? This is definitely something that we hope is addressed? Asking a client to constantly back up their work isn’t really a sustainable solution at the corporate level.

Thanks for sharing this, ​@Skild ! The extra detail is really helpful, especially the email notification showing different content than what ended up in the file, and the temporary visibility difference on your client's end. 

With a second report now, this does look like it could be a broader issue rather than isolated to one account, so I've flagged this additional report internally with our Specs team for visibility.

That said, I'd still recommend submitting a bug report through the Support Hub for your specific case as mentioned above: Support Hub → type "Report a bug, Contact an agent" → Click "Start a chat", and include:

• The URL of the affected file, with Can View access granted to support-share@figma.com
• A screenshot of the email notification showing the original content
• A screenshot of what remained in the file
• Roughly how long after saving the content disappeared for your client

Having both the email notification and the in-file result will be especially useful for the team to compare against and try to reproduce it. Appreciate you flagging this, it's helpful context as this gets looked into! Thank you