Skip to content

Progression tab goes blank and skips animation on tab switch in Account/Profile modal #5971

Open

Description

@LoSt543215543

Describe the bug
When navigating the Progression tab in the Account Settings or Player Profile modal:

  1. On the first open, the tab loads and plays the entrance pop-in animation.
  2. When switching away to another tab (such as Stats, Games, or Account) and returning to the Progression tab, the modal displays a blank black void for ~0.5–1s while re-fetching /users/@me.
  3. Once the network request finishes, the content abruptly snaps onto the screen with zero transition because the animation is suppressed on subsequent visits.

Root Causes

  1. Black void / Network delay: In ProfileProgression.loadTrack(), this.ready is reset to false, which causes render() to return nothing (blank void). loadOwnAccount() calls invalidateUserMe() on every tab mount, forcing an un-cached network request to /users/@me even though the modal already has the user profile in memory.
  2. Missing animation on return: Both ProfileProgression and ProfileCard guard entrance animations using popKey / openKey formatted as account-${openCount}. openCount only increments when the modal itself opens, not when switching tabs. When returning to the tab, key === lastPoppedKey, so the animation is skipped.

To Reproduce

  1. Open Account Settings.
  2. Click on the Progression tab (observe the pop-in animation).
  3. Switch to the Stats tab.
  4. Switch back to the Progression tab.
  5. Notice the tab is pitch-black for up to a second before snapping in with no animation.

Expected behavior

  • Tab switches should render cached account data immediately (0ms delay, no black screen).
  • If data is ever pending on cold start / slow networks, render a loading spinner instead of an empty black void.
  • Tab transitions into Progression and Stats should smoothly play their entrance animations (Progression pop-in and Profile Card pulse flourish).

Activity

  1. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Hi @LoSt543215543, thanks for opening this issue. It hasn't been approved by a maintainer yet — we'll get back to you shortly to either milestone it (approval) or close it.

    — Automated. See CONTRIBUTING.md.

  2. added this to the Backlog milestone on Oct 16, 2026
  3. added
    approvedApproved for a PR, if you assigned to the issue.
    and removed
    not-approvedThis issue has NOT been approved by the maintainers.
    on Oct 16, 2026
  4. LoSt543215543 commented on Oct 16, 2026

    @LoSt543215543
    ContributorAuthor

    lewis in case you don't want to do it, I have it finished. I forgot to mark myself as wanting to do it.

  5. LoSt543215543 commented on Oct 22, 2026

    @LoSt543215543
    ContributorAuthor

    Noticed this hasn't been worked on for a week, if you want I can do this instead?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

approvedApproved for a PR, if you assigned to the issue.

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions