Skip to content

fix: reorder columns in Leaderboard component for consistency#368

Open
JoshuaMoelans wants to merge 2 commits intomainfrom
fix/leaderboard_column_order
Open

fix: reorder columns in Leaderboard component for consistency#368
JoshuaMoelans wants to merge 2 commits intomainfrom
fix/leaderboard_column_order

Conversation

@JoshuaMoelans
Copy link
Copy Markdown
Member

To be consistent with the 'Received/Sent' toggle at the top

Before

Screenshot 2025-12-12 at 10 13 50

After
Screenshot 2025-12-12 at 10 15 10

@JoshuaMoelans JoshuaMoelans requested a review from a team as a code owner December 12, 2025 09:16
Copy link
Copy Markdown

@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.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

</th>
<th scope="col" class="hidden md:table-cell py-3.5 px-3 text-right text-sm font-semibold">
Sent
</th>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Header and data cell CSS classes are mismatched

Low Severity

The column reorder used two different strategies: the <th> elements were physically moved (keeping their CSS), but the <td> elements only had their text content swapped (keeping their CSS in place). This means the positional styling classes (relative, pl-3 vs px-3, pr-4) are now mismatched between each header and its data cells. For example, the "Received" header has relative pl-3 while its data cell has px-3, and the "Sent" header has px-3 while its data cell has relative pl-3 pr-4.

Additional Locations (1)

Fix in Cursor Fix in Web

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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants