feat(core): corner-shape css property for continuous corners on iOS - #11365
Merged
Merged
Conversation
|
View your CI Pipeline Execution ↗ for commit 275a118
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
commit: |
NathanWalker
force-pushed
the
feat/corner-shape
branch
from
August 26, 2026 18:58
37d7f66 to
cf31f9d
Compare
Adds the CSS Borders Level 4 corner-shape property with the round and squircle keywords. squircle maps to kCACornerCurveContinuous - Apple's smooth corner curve used across system UI - and round keeps the circular default, so nothing changes for existing apps. The curve applies on the uniform-border fast path, where corners render through layer.cornerRadius. The path-drawn branches - non-uniform borders, box-shadow outlines, clip masks - still build circular arcs, so a squircle view keeps circular corners there until those generators learn to emit the continuous curve. Android always renders round. CSS: corner-shape only became addressable on the web recently (Chrome 139, Safari's proposal), so round | squircle is the supported subset.
edusperoni
force-pushed
the
feat/corner-shape
branch
from
August 26, 2026 19:09
cf31f9d to
275a118
Compare
2 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
What is the current behavior?
Corners always render as circular arcs —
CALayer.cornerCurveis never set, so layers use thekCACornerCurveCirculardefault. Apps that want Apple's smooth "continuous" corners (the squircle look used across iOS system UI: app icons, alerts, cards) have to patch@nativescript/coredist output or pokeview.ios.layer.cornerCurvemanually.What is the new behavior?
A new
corner-shapeCSS property — the CSS Borders Level 4 property recently shipped on the web (Chrome 139; proposed by Safari) — with theround | squirclekeyword subset:squirclemaps tokCACornerCurveContinuouson iOS;round(the default) keepskCACornerCurveCircular, so existing apps are visually unchanged.Backgroundflow:Style.cornerShape→backgroundInternal.withCornerShape()→ applied inbackground.ios.tson the uniform-border fast path where corners render vialayer.cornerRadius.round) — there is no native equivalent.Known limitation (documented in the commit): the path-drawn branches — non-uniform borders, box-shadow outlines, clip masks — build circular-arc
UIBezierPaths and are unaffected, so a squircle view falls back to circular corners in those combinations. Teaching those generators to emit the continuous curve (a superellipse approximation) can land as a follow-up.3 new unit tests (default, squircle round-trip to
Background, unknown-keyword rejection); full suite passing (403).