Image with Aspect of AspectFill in CollectionView item is not clipped to the item bounds
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 290
Description
### Description
I created a new MAUI app in Visual Studio Community 2022 V 17.2.0 Preview 6.0, and Microsoft.Maui.Dependencies/Extensions 6.0.300-rc.2.5513. I then added a CollectionView based on demo code at https://docs.microsoft.com/en-us/dotnet/maui/user-interface/controls/collectionview/layout. The app code is public at https://github.com/gbarkerz/MyMauiAppAccessibility. The image contained within each item has fixed dimensions of 60x60, and an Aspect of AspectFill.
When the app is run, the displayed image bounds are not clipped at 60x60, rather the image overflows the Image bounds, as shown in the image below. I would expect the displayed image to be clipped at the Image bounds.

### Steps to Reproduce
1. Create a new MAUI app in Visual Studio Community 2022 V 17.2.0 Preview 6.0, and Microsoft.Maui.Dependencies/Extensions 6.0.300-rc.2.5513.
2. Add a CollectionView based on demo code at https://docs.microsoft.com/en-us/dotnet/maui/user-interface/controls/collectionview/layout, and have each item contain an Image with fixed bounds and an Aspect of AspectFill.
3. Run the app and note that the displayed image overflows the Image bounds.
### Version with bug
Release Candidate 2
### Last version that worked well
Unknown/Other
### Affected platforms
iOS
### Affected platform versions
iOS 15
### Did you find any workaround?
_No response_
### Relevant log output
_No response_
Contributor guide
Research direction
Start with the public MyMauiAppAccessibility reproduction and the CollectionView layout sample linked in the issue. Run the app on iOS 15 and inspect the CollectionView item Image configured with fixed 60x60 bounds and AspectFill. Done means the displayed image is clipped to the Image bounds instead of overflowing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, ios
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100