[Bug]: SVG window-frame header band rounds its bottom corners
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Read crates/renderer/src/svg.rs at the single-panel header around lines 197–203, then compare the split-panel header around lines 441–446 and the canvas rendering behavior described in the issue. Adjust SVG header rendering so its bottom corners are square while the top follows the card shape. Export both single- and split-panel SVGs and compare their header edges with PNG output.
Written by the indexing model from the issue text.
Description
What happened?
In the SVG export, the window-frame header band has rounded bottom corners. In the canvas (PNG) output the same band is clipped to the card shape, so its bottom corners are square. The two export formats therefore do not match: the SVG shows small notches at the bottom corners of the header band.
Steps to reproduce
- Export SVG with the window frame enabled (default).
- Open the file and look at the header band above the code.
- Compare with the PNG export of the same content.
Expected behavior
The header band bottom edge is straight, identical to the canvas rendering.
Actual behavior
The SVG header band is drawn as a standalone rounded rect (rx set to the card corner radius), which rounds all four corners including the bottom two. Canvas clips the band to the card path, so it has no bottom rounding.
Where did it go wrong?
SVG export
Settings
Window frame enabled. Any theme. Most visible on dark themes where the band tint contrasts with the card background.
Browser
Not browser specific.
CodeFrame version
0.7.0
Console output or extra context
References:
crates/renderer/src/svg.rs:197-203(single panel header)crates/renderer/src/svg.rs:441-446(split panel header)
Suggested fix: wrap the header in a <clipPath> that references the card shape, or emit a path that rounds only the top corners.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from suradet-ps/codeframe
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
suradet-ps/codeframe#40 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
suradet-ps/codeframe#36 ·
Maintainers usually reply within 1 day
-
[Bug]: Target width input clamps the value on every keystrokePossibly taken @AnushreeKasturi claimed this today. Openbug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
suradet-ps/codeframe#37 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
suradet-ps/codeframe#38 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
suradet-ps/codeframe#30 ·
Maintainers usually reply within 1 day
All issues in suradet-ps/codeframe
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pop-os/cosmic-comp#2956 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:release criticality:p3 documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
registrystack/registry-stack#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
libp2p/rust-libp2p#6694 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EmbarkStudios/cargo-deny#910 ·