Skip to content

chore(website): fix border radius issue in CSS for design consistency#7993

Merged
serhalp merged 3 commits intomainfrom
agent-issue-in-css-for-design-consistency-9a49
Mar 10, 2026
Merged

chore(website): fix border radius issue in CSS for design consistency#7993
serhalp merged 3 commits intomainfrom
agent-issue-in-css-for-design-consistency-9a49

Conversation

@netlify-coding
Copy link
Copy Markdown
Contributor

@netlify-coding netlify-coding Bot commented Mar 5, 2026

🔗 View agent run: https://app.netlify.com/projects/cli/agent-runs/69aa03b45127da9aeced9a49

🤖 Agent: Claude

💬 Prompt: We need to display the border radius CSS prop

The top border on left and right is breaking the design https://app.screencast.com/WJXmHnilxEgjC

Lets just display or remove it please

{
.expressive-code .frame, .expressive-code pre {
/* ...

Result: Restored border-radius: var(--smallRadius) on .expressive-code .frame and .expressive-code pre so that regular code blocks retain their rounded corners. Added a more specific rule targeting .expressive-code .frame.is-terminal pre to set border-top-left-radius: 0 and border-top-right-radius: 0 only on terminal-style code blocks. This fixes the visual issue where the pre element's top corners were visibly rounded beneath the figcaption header bar in terminal code boxes, while leaving all other code block styles unaffected.

@netlify-coding netlify-coding Bot requested review from a team as code owners March 5, 2026 22:44
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 5, 2026

📝 Walkthrough

Walkthrough

This PR adds a CSS rule override for terminal-styled code blocks in the custom stylesheet. The change targets .expressive-code .frame.is-terminal pre elements to set the top-left and top-right border radii to 0, which removes the rounded corners from the top of terminal code frames while preserving other border-radius values elsewhere.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description is directly related to the changeset, providing context about the CSS border-radius issue, the design problem being fixed, and the specific solution implemented.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately describes the main change: fixing a border-radius CSS issue for design consistency in terminal code blocks.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch agent-issue-in-css-for-design-consistency-9a49

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

@DavidWells
Copy link
Copy Markdown
Contributor

Fixes this

image

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Mar 5, 2026

📊 Benchmark results

Comparing with e00d1f0

  • Dependency count: 1,102 (no change)
  • Package size: 354 MB (no change)
  • Number of ts-expect-error directives: 362 (no change)

@serhalp serhalp changed the title Fix border radius issue in CSS for design consistency chore(website): fix border radius issue in CSS for design consistency Mar 9, 2026
@serhalp serhalp enabled auto-merge (squash) March 9, 2026 13:04
@serhalp serhalp removed request for a team March 10, 2026 13:01
@serhalp serhalp merged commit 1255739 into main Mar 10, 2026
71 checks passed
@serhalp serhalp deleted the agent-issue-in-css-for-design-consistency-9a49 branch March 10, 2026 13:19
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.

3 participants