Skip to content

feat: squircle corners#2

Open
mixflavor wants to merge 1 commit into
mainfrom
feat/squircle-corners
Open

feat: squircle corners#2
mixflavor wants to merge 1 commit into
mainfrom
feat/squircle-corners

Conversation

@mixflavor

Copy link
Copy Markdown
Contributor

What

Adds continuous-curvature (squircle) corners to demodeck's dark control-panel surfaces via CSS corner-shape: squircle, layered on top of the existing border-radius values.

A single inherited custom property drives it:

:root { --corner: squircle; }
/* then, next to each finite border-radius: */
corner-shape: var(--corner);

Applied to the finite-radius surfaces: .control-panel, .dd-ghlink, .option-group, .option-btn, .dd-select, .live-console, .code-snippet-box, .copy-btn, .header-edit-btn, .popover-card, .hex-text-input, .text-input.

Left untouched (intentionally round): pills (.dd-badge, .toggle-container, range track, .slider-toggle) and circles (.color-btn, .color-picker-label, toggle knob, terminal dots, scrollbar thumb).

Caveat — zero visual regression

corner-shape is Chromium-only as of mid-2026. Safari/WebKit and Firefox ignore it and keep the plain border-radius arc, and corner-shape requires a non-zero border-radius to take effect, so border-radius still both sizes the corner and serves as the graceful fallback. This is pure progressive enhancement.

Mirrors the squircle standard already shipped in CVERInc/cver.net and liquidframe.

Add CSS corner-shape: squircle (continuous-curvature corners) on top of the
existing border-radius for demodeck's finite-radius surfaces: control panel,
ghlink, option group + buttons, select, live console, code snippet box, copy
button, header edit button, popover card, hex input, and text input.

Driven by a single inherited --corner token so corner-shape stays consistent
and disappears cleanly where it shouldn't apply. Pills (badge, toggle, range
track) and circles (color dots, toggle knob, scrollbar) are left untouched.

Progressive enhancement only: corner-shape is Chromium-only as of mid-2026;
Safari/WebKit and Firefox ignore it and keep the plain border-radius arc, so
there is zero visual regression.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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