Reacting to a deeplinked note re-renders it, causing scrolling and GLQL issues

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Reacting to a deep-linked comment seems to re-render the content of the comment.

This can cause the page to scroll away and causes GLQL Views to re-render, which takes time and spends against the 20-per-page limit.

The effect is that:

  • The user has to scroll back to and find the comment.
  • Previously rendered and visible GLQL Views are now reloading.
  • If there are a number of GLQL Views, some won't load at all.

This only appears to happen on the first reaction after page load. However, it also looks like the comment is already loaded twice by that stage (once on page load, once after autoscroll).

Reproduction

I discovered this after reacting to https://gitlab.com/gitlab-org/plan-stage/product/-/issues/146#note_2403753278.

  1. Go to this link
  2. Let yourself be scrolled to the note
  3. React to the note
Edited by 🤖 GitLab Bot 🤖