-
Notifications
You must be signed in to change notification settings - Fork 1.9k
StrokeLineJoin values have no effect on iOS and Mac platform #29743
Copy link
Copy link
Open
Labels
area-controls-borderBorderBorderpartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/iosplatform/macosmacOS / Mac CatalystmacOS / Mac Catalysts/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Milestone
Metadata
Metadata
Assignees
Labels
area-controls-borderBorderBorderpartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/iosplatform/macosmacOS / Mac CatalystmacOS / Mac Catalysts/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Description
The StrokeLineJoin property on the Border control does not have any visual effect when running on iOS and macOS Catalyst platforms. The join style appears unchanged regardless of the value provided (Miter, Bevel, or Round), while it works correctly on Android and Windows.
IOS:
Windows:
Steps to Reproduce
Expected Behavior:
Changing StrokeLineJoin should affect how the corners of stroked shapes are rendered—e.g., sharp (Miter), beveled (Bevel), or rounded (Round)—across all platforms.
Actual Behavior:
On iOS and macOS, the stroke join style remains visually unchanged despite assigning different StrokeLineJoin values.
Link to public reproduction project repository
No response
Version with bug
10.0.0-preview.4
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
No response
Affected platforms
iOS, macOS
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output