fix: truncate long URLs with ellipsis

[lalkai]

Hi, I came across this small UI bug on your website by chance and wanted to help fix it.
This pull request applies a CSS fix to truncate overly long URLs with an ellipsis (...) so they don’t overflow outside the container.
If this change is not needed, feel free to close this PR.

Before

After

Summary by CodeRabbit

• Style
  • Improved layout and readability by enforcing single-line truncation with ellipsis for main content and ring links.
  • Prevented text wrapping and overflow, ensuring long text is neatly capped within available space.
  • Aligned elements consistently (inline-block, bottom alignment) for a cleaner visual presentation.
  • Enhances usability on smaller viewports without altering functionality.

[coderabbitai]

Walkthrough

Adds single-line truncation and inline-block layout to two selectors in index.css. For main and #ring a, sets display: inline-block, max-width: calc(100% - 35px), white-space: nowrap, overflow: hidden, text-overflow: ellipsis, and vertical-align: bottom. No other selectors are changed.

Changes

Cohort / File(s)	Summary
CSS truncation and layout tweaks index.css	Adds inline-block, max-width, nowrap, hidden overflow, ellipsis, and bottom alignment to main and #ring a selectors to enforce single-line truncated text and alignment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I nuzzle the CSS, whiskers neat and small,
Trimming lines to ellipses, no wraps at all.
Inline I hop, aligned at the bottom seam,
Max-width fences keep text in a stream.
A tidy warren of styles—swift, compact, serene. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

index.css (2)

97-102: Consider display:block + width:100% to avoid magic numbers and expand the clickable area.

Using inline-block with max-width: calc(100% - 35px) relies on a hard-coded 35px that may drift as surrounding spacing changes. A block-level link with width: 100% avoids the magic number, typically makes the entire row clickable, and simplifies layout across column-count breakpoints.

Suggested tweak within this hunk:

-  display: inline-block;
-  max-width: calc(100% - 35px);
+  display: block;
+  width: 100%;
   white-space: nowrap;
   overflow: hidden;
   text-overflow: ellipsis;
-  vertical-align: bottom;
+  box-sizing: border-box;

And, because width: 100% plus the current negative margins can overflow, consider adjusting the margin outside this hunk (Line 92):

-  margin: -3px;
+  margin: 0;

Net effect:

• Removes the 35px “magic number.”
• Ensures the highlight/background and hit target span the full list width.
• Keeps truncation behavior intact across all breakpoints.

---

97-102: Sanity-check across breakpoints and focus states.

• Verify truncation at viewport widths that change column-count (≥960, ≥1200, ≥1400, ≥1600, ≥1800px) to ensure no unexpected wrapping/overflow.
• Confirm that “current/target” styles (#ring li[data-current] a, #ring li:target a) still render backgrounds as intended with truncation.
• If you later introduce custom focus styles (e.g., box-shadow), note that overflow: hidden can clip shadows; prefer outline for focus rings to avoid clipping.

If helpful, I can open a follow-up to add a :focus-visible style and/or a tooltip pattern so the full URL remains discoverable when truncated.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 61bc09b and 6f51a13.

📒 Files selected for processing (1)

• index.css (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (1)

index.css (1)

97-102: Ellipsis fix is on point for long URLs.

The combination of white-space: nowrap, overflow: hidden, and text-overflow: ellipsis will correctly truncate overly long anchors. Good targeted change.

[dtinth]

Thanks krub, @lalkai!