Fixed Rectangle appears blurred on iOS and macOS when its bounds are changed at runtime #32140
+93
−0
Conversation
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
…changed at runtime
|
Hey there @@Dhivya-SF4094! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
dotnet-policy-service
bot
added
the
partner/syncfusion
sheiksyedm
added
area-drawing
jsuarezruiz
requested changes
Oct 22, 2025
| { | ||
| BackgroundColor = UIColor.Clear; | ||
| // Redraw the shape when bounds change to prevent blur during resizing in container layouts. | ||
| ContentMode = UIViewContentMode.Redraw; |
There was a problem hiding this comment.
Mnnn, UIViewContentMode.Redraw triggers Draw(CGRect) every time bounds change, including:
- Layout passes (multiple per frame)
- Animations (60fps = 60 redraws/second)
- Parent container resizing
- Keyboard appearance/dismissal
- Orientation changes
- Safe area inset changes
- ScrollView scrolling (if shape is inside)
Shape rendering is already expensive:
- Path calculation
- Fill rendering
- Stroke rendering
- Shadow/gradient effects
- Anti-aliasing
For complex shapes (Polygon, Path with many points), this could cause performance issues. The key question is do all shapes have this blurring issue? If is only Rectangle, can move the fix to the Rectangle.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Note
Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!
Issue Details:
When a Rectangle inside an AbsoluteLayout is initially set to (0, 0, AutoSize, AutoSize) and later updated to (50, 50, 100, 100) at runtime, it appears blurred after the bounds change.
Root Cause
The issue occurs because the native view’s layer reuses previously rendered content and scales it instead of redrawing. Since the Draw(CGRect) method is not automatically called when bounds change, the default scaling behavior (UIViewContentMode.ScaleToFill) causes pixelation instead of a proper redraw.
Description of Change
Updated MauiShapeView on iOS/macOS to set ContentMode to UIViewContentMode.Redraw.
This ensures that the shape is redrawn cleanly whenever its bounds change, preventing blur or pixelation.
Validated the behaviour in the following platforms
Issues Fixed:
Fixes #32042
Screenshots