[Windows] Fixed Unstable order of Flyout Items with conditional visibility #29197
Conversation
|
Hey there @@SubhikshaSf4851! 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
| { | ||
| FlyoutItems.Add(item); | ||
| if (index < FlyoutItems.Count) |
There was a problem hiding this comment.
Store FlyoutItems.Count in a variable to minimize repeated property accesses.
There was a problem hiding this comment.
I have updated the changes per your suggestion.
| var item = newItems[index]; | ||
| var flyoutItemIndex = FlyoutItems.IndexOf(item); | ||
|
|
||
| if (flyoutItemIndex == -1) |
There was a problem hiding this comment.
Not big performance differences, but can simplify this using Contains:
if (!FlyoutItems.Contains(item))
{
// Use Insert when within bounds, otherwise Add
if (index < count)
{
FlyoutItems.Insert(index, item);
}
else
{
FlyoutItems.Add(item);
}
}
NOTE: count is a variable with the FlyoutItems.Count value.
There was a problem hiding this comment.
I have updated the changes per your suggestion.
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| App.WaitForElement("button"); | ||
| App.Tap("button"); | ||
| App.ShowFlyout(); | ||
| VerifyScreenshot(); |
There was a problem hiding this comment.
Snapshots already available in the latest build:
For example:
There was a problem hiding this comment.
I have committed the pending snapshots
|
/azp run MAUI-UITests-public |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Root Cause:
When the visibility of a Flyout item is changed, the UpdateMenuItemSource method simply adds the item to the end, resulting in the original order of the Flyout items being mismatched.
Description of change:
Instead of adding the item, I have retrieved its original position and inserted it back into the Flyout items accordingly, which results the original order being maintained.
Tested the behavior in the following platforms:
Issue Fixed:
Fixes #23834
Issue23834_BeforeFix.mp4
Issue23834_AfterFix.mp4