Skip to content

Conversation

@dipeshmsft
Copy link
Member

This is an API Spec PR for the proposed SplitMenuFlyoutItem control.

PR Type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Description

The SplitMenuFlyoutItem control is proposed to be a new addition to the WinUI library, designed to provide a split button experience within a menu flyout. This control derives from MenuFlyoutItem and introduces a dual-button interface consisting of a primary button and a flyout button.

Motivation and Context

This functionality will allow developers to expose a default primary action while also offering additional options through an attached dropdown — ideal for condensing complex functionality into a smaller footprint and saving overall menu length.

How Has This Been Tested?

  • I have performed a self-review of my own code
  • I have added tests to cover my changes

Screenshots (if appropriate):

Attached in the document.

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Oct 30, 2025
@eduardobragaxz
Copy link

AppBarSplitButton would be nice too 👀

@michael-hawker michael-hawker moved this to API Review - Gathering Feedback in API Specs Review Oct 30, 2025
@michael-hawker
Copy link
Collaborator

I've added this to the public api review process board: https://aka.ms/winappsdk/api-specs-review

This PR will be open for feedback for a month from its opening: October 30th – November 30th

FYI @dipeshmsft

@michael-hawker michael-hawker added SpecInReview and removed needs-triage Issue needs to be triaged by the area owners labels Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: API Review - Gathering Feedback

Development

Successfully merging this pull request may close these issues.

3 participants