Skip to content

ref(nav) realign indicators#111816

Open
JonasBa wants to merge 1 commit intomasterfrom
jb/nav/indicators
Open

ref(nav) realign indicators#111816
JonasBa wants to merge 1 commit intomasterfrom
jb/nav/indicators

Conversation

@JonasBa
Copy link
Copy Markdown
Member

@JonasBa JonasBa commented Mar 30, 2026

This broke with our change to the new indicators, so I'm updating each element's location and the button overflow accordingly

@JonasBa JonasBa requested a review from a team as a code owner March 30, 2026 19:27
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 30, 2026
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.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

> = hasPageFrame
? layout === 'mobile'
? {top: '0', right: '0'}
: {top: '0', right: '0'}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Redundant ternary produces identical values for both branches

Medium Severity

When hasPageFrame is true, the layout === 'mobile' ternary on lines 324–326 returns {top: '0', right: '0'} for both branches, making the condition dead code. Given that the non-hasPageFrame path does differentiate between mobile (left: '11px', offset top) and desktop (top: '0', right: '0'), this looks like a copy-paste error where the hasPageFrame + mobile case was not given its intended distinct positioning.

Fix in Cursor Fix in Web

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.

1 participant