Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • stacks stacks
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 173
    • Issues 173
    • List
    • Boards
    • Service Desk
    • Milestones
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • YourHeadYourHead
  • stacksstacks
  • Issues
  • #542
Closed
Open
Issue created Jun 28, 2020 by Isaiah Carew@isaiahcarew☕Owner

clicks after a page change, but before the refresh completes, can upset the selection

a page change forces a full page refresh drawing the selection outline on whatever was selected the last time the page was visited.

a click that changes the selection forces a fast DOM update of only the classes of the affected stacks: deselecting the current selection and selecting the new selection.

there is a race between the fast DOM update and the slow page refresh. the selection update does not wait until the refresh has completed. this can result in the DOM being out of sync with the controller's selection.

Assignee
Assign to
Time tracking