-
Notifications
You must be signed in to change notification settings - Fork 717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CornerRadius
alignment
#10263
Comments
Is this a duplicate of #6891? |
CornerRadius
rendering does not take BorderThickness
into accountCornerRadius
alignment
@Youssef1313 this is a superset of that issue - it includes additional edge cases, so I will copy include the info here and close it 👍 |
From #6891 Current behaviorEdge case to fix on all platforms where Inner Radius doesn't match UWP when BorderThickness >= CornerRadius Expected behaviorInner Radius calculations should match UWP behaviors when BorderThickness >= CornerRadius How to reproduce it (as minimally and precisely as possible)
|
https://9elements.github.io/fancy-border-radius/#30.24.62.59--575.575
|
Duplicate issue: Current behavior Expected behavior How to reproduce it (as minimally and precisely as possible) Workaround |
This issue effects the RangeSelector control within the Windows Community Toolkit, as reported by Niels in the duplicate #9490. |
@MartinZikmund Handing this back to you for iOS/macOS |
We're still seeing this in WASM in the WCT: CommunityToolkit/Windows#386 |
Current behavior
On most targets
CornerRadius
does not adjust based onBorderThickness
, inner radius is not applied correctly, and outer radius is not calculated correctly when neighboring corner radii have total size greater than element size.Expected behavior
Outer corner radius ==
CornerRadius
+BorderThickness
/ 2Inner corner radius ==
CornerRadius
-BorderThickness
/ 2When two neighboring corners would "overlap", their size is "fairly" distributed along the side of the element.
For accurate implementation that exactly adheres to UWP/WinUI see #10260
How to reproduce it (as minimally and precisely as possible)
No response
Workaround
No response
Works on UWP/WinUI
No response
Environment
No response
NuGet package version(s)
No response
Affected platforms
WebAssembly, Android, iOS, macOS (AppKit), Mac Catalyst
Skia targets have the correct rendering since #10260
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: