Skip to content

fix(cross-events): Correct styling based off date selection#116124

Merged
nsdeschenes merged 2 commits into
masterfrom
nd/fix-cross-events-fix-styling-based-off-date-selection
May 25, 2026
Merged

fix(cross-events): Correct styling based off date selection#116124
nsdeschenes merged 2 commits into
masterfrom
nd/fix-cross-events-fix-styling-based-off-date-selection

Conversation

@nsdeschenes
Copy link
Copy Markdown
Contributor

@nsdeschenes nsdeschenes commented May 25, 2026

The goal of this PR is to tweak the styles for the cross-event query section based off of the period selection. There are a couple issues currently when selecting an exact date range so this PR tweaks the styles based off of that condition.

Before After
Relative Date Screenshot 2026-05-25 at 09 04 53 Screenshot 2026-05-25 at 09 05 20
Absolute Date Screenshot 2026-05-25 at 09 06 16 Screenshot 2026-05-25 at 09 06 26
Absolute Date w/time Screenshot 2026-05-25 at 09 07 21 Screenshot 2026-05-25 at 09 07 29

Constrain the metric selector and query builder columns so long content can shrink within the cross-event metric row.
Render cross-event rows in a separate grid when the date filter uses explicit start and end dates so the independent date controls align with each row.
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 25, 2026
@nsdeschenes
Copy link
Copy Markdown
Contributor Author

@cursor review

@nsdeschenes
Copy link
Copy Markdown
Contributor Author

@sentry review

Copy link
Copy Markdown
Contributor

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit 0250fc2. Configure here.

@github-actions
Copy link
Copy Markdown
Contributor

📊 Type Coverage Diff

✅ No new type safety issues introduced. Coverage: 93.57%

@nsdeschenes nsdeschenes marked this pull request as ready for review May 25, 2026 12:14
@nsdeschenes nsdeschenes requested a review from a team as a code owner May 25, 2026 12:14
Copy link
Copy Markdown
Member

@nikkikapadia nikkikapadia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one comment

Comment on lines +192 to +198
{hasCrossEvents && !hasAbsoluteDateSelection ? (
<SpansTabCrossEventSearchBars />
) : null}
</Grid>
{hasCrossEvents && hasAbsoluteDateSelection ? (
<SpansTabCrossEventSearchBars hasIndependentDateColumn />
) : null}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{hasCrossEvents && !hasAbsoluteDateSelection ? (
<SpansTabCrossEventSearchBars />
) : null}
</Grid>
{hasCrossEvents && hasAbsoluteDateSelection ? (
<SpansTabCrossEventSearchBars hasIndependentDateColumn />
) : null}
{hasCrossEvents ? (
<SpansTabCrossEventSearchBars hasIndependentDateColumn={hasAbsoluteDateSelection} />
) : null}

can we just do this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried that initially but things become unaligned and a little gross :/

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

boooo welp

@nsdeschenes nsdeschenes merged commit 0b8586e into master May 25, 2026
73 checks passed
@nsdeschenes nsdeschenes deleted the nd/fix-cross-events-fix-styling-based-off-date-selection branch May 25, 2026 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants