dotnet / dotnet/maui

[Enhancement] Add Flyout Title and FlyoutIcon when FlyoutDisplayOptions="AsMultipleItems" is set.

Open
#34,231 0 comments 1 reaction 0 assignees View on GitHub
proposal/open
Dominant language
C#
Stars
23.3k
Forks
2k
Avg merge
1d 14h
Merged PRs (30d)
296

Description

### Description

When grouping flyout times in a menu, it would be nice if the "Title" and "Icon" properties (already present) were used as a header/title for the items underneath it.

I am basing this issue on Xamarin.Forms [#13343](https://github.com/xamarin/Xamarin.Forms/issues/13343)

### Public API Changes

The Title field is already present in the API; it is not used when FlyoutDisplayOptions="AsMultipleItems" is set.

```xaml


```

### Intended Use-Case

#### Use-Case 1 (From the original Xamarin.Forms issue)
The flyout menu can be hard to read when there are a lot of items. Being able to group them with a header would be ideal. In the image below, adding "MyTitle" to the grouping would make it easier to find a menu item. My online banking app uses such an approach.

Image

#### Use-Case 2
In this one, I wish to have a header called "Recommended Mechanics, Dealerships and Stores" with either nested or collapsible items. The routes and ContentTemplates are just placeholders

Image

```xaml



```

An example of it potentially working could be similar to how WinUI uses NavItems

Image

Contributor guide

Open the contributing guide

Research direction

Start by tracing how FlyoutItem and FlyoutDisplayOptions="AsMultipleItems" are handled in .NET MAUI's flyout navigation. Review the existing Title and Icon properties and compare the requested grouping behavior with the linked Xamarin.Forms issue and WinUI example. Done means grouped flyout items display the parent title and icon consistently across supported platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
frontend
Issue type
Feature
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.