ref(replays): reduce bottom bar #104246
Open
ref(replays): reduce bottom bar #104246
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Adjusted the dimensions of placeholders in various components for consistency. - Updated padding in the header for improved layout. - Refactored ReplayDetailsUserBadge to utilize a new layout structure and link query handling. - Added Flex container to enhance loading state presentation in ReplayDetailsMetadata. These changes aim to enhance the UI and maintain a cohesive design across replay components.
github-actions
bot
added
the
Scope: Frontend
…ation Modified ReplayPreviewPlayer and ReplayTable components to utilize linkQuery for constructing navigation paths. This change enhances the clarity of the code and ensures consistent handling of query parameters across replay-related components.
❌ 2 Tests Failed:
View the top 2 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
…replay-ui-3-shrink-bottom-header-4
jerryzhou196
added a commit
that referenced
this pull request
Dec 2, 2025
…ation (#104247) > Related to [REPLAY-814: Implement new UI for Replay Page](https://linear.app/getsentry/issue/REPLAY-814/implement-new-ui-for-replay-page) Change columns to support generic link objects. This is used in #104246 to maintain the user email search feature.
… and update styling in replayMetaData
…yling in timestamp display
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| columnIndex={0} | ||
| showDropdownFilters={false} | ||
| to={linkQuery} | ||
| /> |
Contributor
There was a problem hiding this comment.
Bug: Analytics event incorrectly tracks navigation direction
The ReplaySessionColumn.Component is designed for replay list tables and fires trackAnalytics('replay.list-navigate-to-details', ...) with referrer_table: 'main' on click. When reused in the replay details header, this tracks the wrong event - the actual navigation is from the details page to the list page (when searchQuery exists), not list to details. The original code had no analytics tracking on this link, so the PR introduces misleading analytics data.
…rom ReplaySessionColumn
| platform: project?.platform, | ||
| organization, | ||
| referrer, | ||
| referrer_table: 'main', |
Member
There was a problem hiding this comment.
why did we get rid of referrer_table?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on #104247
This updates the bottom bar to