-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[iOS/Mac] Fixed the Border Rendering issues in CollectionViewHandler2 #27801
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
Conversation
|
Hey there @Ahamed-Ali! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| using Microsoft.Maui.Controls; | ||
| using Microsoft.Maui.Controls.Handlers.Compatibility; | ||
| using Microsoft.Maui.Controls.Handlers.Items; | ||
| using Microsoft.Maui.Controls.Handlers.Items2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build is facing:
D:\a\_work\1\s\src\Controls\tests\DeviceTests\Elements\CollectionView\CollectionViewTests.cs(13,40): error CS0234: The type or namespace name 'Items2' does not exist in the namespace 'Microsoft.Maui.Controls.Handlers' (are you missing an assembly reference?) [D:\a\_work\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net9.0-windows10.0.20348.0]
D:\a\_work\1\s\src\Controls\tests\DeviceTests\Elements\CollectionView\CollectionViewTests.cs(13,40): error CS0234: The type or namespace name 'Items2' does not exist in the namespace 'Microsoft.Maui.Controls.Handlers' (are you missing an assembly reference?) [D:\a\_work\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net9.0-windows10.0.19041.0]
D:\a\_work\1\s\src\Controls\tests\DeviceTests\Elements\CollectionView\CollectionViewTests.cs(13,40): error CS0234: The type or namespace name 'Items2' does not exist in the namespace 'Microsoft.Maui.Controls.Handlers' (are you missing an assembly reference?) [D:\a\_work\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net9.0-android]
9023 Warning(s)
3 Error(s)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Due to Microsoft.Maui.Controls.Handlers.Items2 not being available for Android and Windows, a build error occurred. I have now added a condition to resolve it. Could you please check? @jsuarezruiz
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/rebase |
c607623 to
46a79bb
Compare
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
jsuarezruiz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ahamed-Ali Could you rebase and fix the conflict? Thanks in advance.
|
Since the same changes in this PR were already merged into the main branch in LayoutSubViews by this #28225, I have kept only the test. @PureWeen / @rmarinho / @jsuarezruiz |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| *REMOVED*override Microsoft.Maui.Controls.Handlers.Compatibility.FrameRenderer.SetNeedsLayout() -> void | ||
| *REMOVED*override Microsoft.Maui.Controls.Handlers.Compatibility.FrameRenderer.MovedToWindow() -> void | ||
| override Microsoft.Maui.Controls.Handlers.Compatibility.VisualElementRenderer<TElement>.MovedToWindow() -> void | ||
| override Microsoft.Maui.Controls.Handlers.Compatibility.VisualElementRenderer<TElement>.MovedToWindow() -> void |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can revert this unnecessary change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a change. The same code is only appearing as a change in this PR. When I removed the unshipped code of my fix, this appeared in the PR, and I am unable to remove it. @jsuarezruiz
src/Controls/tests/DeviceTests/Elements/CollectionView/CollectionViewTests.iOS.cs
Show resolved
Hide resolved
|
/rebase |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
jsuarezruiz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you fix the build errors?
C:\a\_work\1\s\src\Controls\tests\DeviceTests\Elements\CollectionView\CollectionViewTests.iOS.cs(19,7): error CS0105: The using directive for 'Microsoft.Maui.Handlers' appeared previously in this namespace [C:\a\_work\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net9.0-ios]
C:\a\_work\1\s\src\Controls\tests\DeviceTests\Elements\CollectionView\CollectionViewTests.iOS.cs(19,7): error CS0105: The using directive for 'Microsoft.Maui.Handlers' appeared previously in this namespace [C:\a\_work\1\s\src\Controls\tests\DeviceTests\Controls.DeviceTests.csproj::TargetFramework=net9.0-maccatalyst]
2 Error(s)
The build errors occurred because the same namespace was used twice. I have now resolved the errors. @jsuarezruiz |
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| *REMOVED*override Microsoft.Maui.Controls.Handlers.Compatibility.FrameRenderer.SetNeedsLayout() -> void | ||
| *REMOVED*override Microsoft.Maui.Controls.Handlers.Compatibility.FrameRenderer.MovedToWindow() -> void | ||
| override Microsoft.Maui.Controls.Handlers.Compatibility.VisualElementRenderer<TElement>.MovedToWindow() -> void | ||
| override Microsoft.Maui.Controls.Handlers.Compatibility.VisualElementRenderer<TElement>.MovedToWindow() -> void |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is no longer necessary, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a change. The same code is only appearing as a change in this PR. When I removed the unshipped code of my fix, this appeared in the PR, and I am unable to remove it. @jsuarezruiz
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/rebase |
d1ef300 to
2e16463
Compare
…#27801) * Fixed the Border Rendering issues in CollectionViewHandler2 * Remove the unwanted namspace * Removed UI test and added the device test * Resolved the build errors * Registered the cv2 handler inside the test to avoid other test failures * Added a Assert.NotNull test * Resolved the conflicts
…#27801) * Fixed the Border Rendering issues in CollectionViewHandler2 * Remove the unwanted namspace * Removed UI test and added the device test * Resolved the build errors * Registered the cv2 handler inside the test to avoid other test failures * Added a Assert.NotNull test * Resolved the conflicts
…#27801) * Fixed the Border Rendering issues in CollectionViewHandler2 * Remove the unwanted namspace * Removed UI test and added the device test * Resolved the build errors * Registered the cv2 handler inside the test to avoid other test failures * Added a Assert.NotNull test * Resolved the conflicts
Root Cause of the issue
arrangedinTemplatedCell2, causing some items to render improperly while scrolling in cv2.Description of Change
arrangedtheVirtual Viewprevents border shape deformation during scrolling and ensures correct rendering in cv2.Same Changes of PR merged into Main
#28225 Since the same changes in this PR were already merged into the main branch in LayoutSubviews, I have kept only the test.
Issues Fixed
Fixes #27608
Tested the behaviour in the following platforms
Screenshot
Polygon
PolygonIssue.mov
Polygonfixed.mov
RoundRectangle
RoundRectangleIssue.mov
RoundRectangleFix.mov