Moved to next comment when resolved

I agree, this functon is frustating, since I have to go back to resolved screen every single time. Hope Figma team will have an option to disable this feature.

Agreed. My step-by-step QA is very different and the forced auto movement is disorienting and disrupts my flow. 👎🏼

Echoing all the opinions above. Super disruptive, wish there’d be a way to turn this behaviour off. Created an account here just so I can post this.

Yeah this is really annoying.

Hey All, thanks for the feedback! 

I hear your frustration. I understand how this can be disruptive to your daily workflow. Because of that, I’ve updated this topic into a feature request and flagged this over to our team for consideration.

We truly appreciate your feedback, and I hope we can introduce a way to make this process less frustrating for our users. 

Is there an estimated timeline for when this feature request will be completed? I agree with the comments above. As it stands, this feature is not very useful and unfortunately increases the time required to complete revision notes in the workflow.

This behavior is awful and makes working harder. Super frustrating. Please prioritize allowing users to disable it. 

Requesting an update on this! If this works for others, fine--but there really should be an opt-out or disable option available for those who don’t work like this. 

Who ever thought this would be a good idea in the first place?

This feature is seriously frustating. Who ever thought and approved this ?

5 months and they still not remove this feature, no wonder their stock dropped

Chiming in to say, please delete this feature. It’s driving me crazy. 

IS THERE ANY UPDATE ON THIS? WE NEED TO BE ABLE TO AT LEAST DISABLE THIS FUNCTION.

OMG, I saw that people were complaining and figured, fine, I’m sure it will get resolved soon. But no, A) I’m now seeing that this is a SIX MONTH OLD thread, and B) THIS BEHAVIOR IS DRIVING ME NUTS. It cannot fathom why your team decided to necessarily have this feature turned on. WTAF.

​@djv is there any progress on this? this is a really disruptive function.

Hi @JanelleH, thanks for the nudge! 
 

To be transparent, this topic is being tracked internally and hasn't been forgotten. The team has confirmed the auto-advance came out of accessibility work for comment pins, and the current thinking is that it should probably only apply when you're navigating by keyboard; not when you resolve a comment with a click. That matches what you've all been describing.

As of this week, the issue has had its priority raised internally and an engineer on the comments team is actively taking a look at it. While I can't promise a fix date or commit to a specific release, please know that the team is doing its best to move this forward. I'll be sure to come back to this thread as soon as we have something more concrete to share. 

​@djv thank you for your prompt response. I want to clarify that I’m not against having accessibility functions (I think everyone across all industries is trying to adhere to ADA Compliancy as much as possible), but I’d like to point out that whoever decided to release this global and automatic this function seems to not actually QA work. Feels like someone in a conference room asked people to call out suggestions to make improvements on the next Figma-version release (“auto-move to the next comment!”) so that it could feel transformative, but kept as a low overhead change. 

As you’re QA’ing work, you want to examine the change’s effect. So when someone comments, for example a layout orientation change, if the comment was completed by the designer ,your instinct is to resolve the comment, but then STAY on the same page so you can give additional feedback on the change (ex. what if it doesn’t work and needs to be reverted? what if the colors in the new orientation need to be swapped? what if the orientation change now affects the flow/look of the next/previous section, so adjustments need to be made? etc.). People who are truly QA’ing edits (not only the change, but the impact on surrounding areas or global elements) are not in a rush to move on to the next comment. We are trying to stay on the page and make additional comments if necessary.

As you can tell from above (and other related topics I see here), this is an issue for many people. I don’t think anyone is asking to have it completely removed, but at the very least it should be a function you can opt in or out of, instead of being an automatic function.