dotnet / dotnet/maui

Rectangle appears blurred on iOS and macOS when its bounds are changed at runtime within an AbsoluteLayout

Open
#32,042 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-drawing has-workaround partner/syncfusion platform/ios platform/macos s/triaged s/verified t/bug
Dominant language
C#
Stars
23.3k
Forks
2k
Avg merge
1d 14h
Merged PRs (30d)
296

Description

Description

When a Rectangle is placed inside an AbsoluteLayout, and its initial AbsoluteLayout.LayoutBounds is set to (0, 0, AutoSize, AutoSize). However, when the layout bounds (new Rect(50, 50, 100, 100)) are updated at runtime, the rectangle becomes blurred after the bounds change.

Steps to Reproduce
  1. Run the attached sample.
  2. Click button to change the bounds value of Rectangle.
  3. See the rectangle renders as blur.

RectangleBlurIssue.zip

Expected Behavior:
The rectangle should remain sharp and render clearly after the layout bounds are updated.

Actual Behavior:
The rectangle becomes blurred after changing the layout bounds at runtime.

Link to public reproduction project repository

No response

Version with bug

10.0.0-preview.4

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

No response

Affected platforms

macOS, iOS

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the attached RectangleBlurIssue.zip sample and reproducing the blur after the Rectangle's AbsoluteLayout bounds change from AutoSize to (50, 50, 100, 100). Trace the Rectangle and AbsoluteLayout runtime update path on iOS and macOS; done means the rectangle remains sharp after the bounds change on both platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, ios, macos
Domain
desktop, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.