microsoft / microsoft/microsoft-ui-xaml

Proposal: Fix WinUI inconsistency

Open
#11,202 4 comments 0 reactions 0 assignees View on GitHub
area-Windowing feature proposal team-Core
Dominant language
C++
Stars
8.4k
Forks
942
Avg merge
2d 7h
Merged PRs (30d)
105

Description

### Title

Cover a missing inconsistency in WinUI3 apps revolving around a menu not being covered.

### Summary

I noticed that on all WinUI 3 apps, for example calculator and photos on windows 11 (any version) a menu pop's up featuring restore, move, minimize, maximize, and close, it uses the win32 menu (or classic menu if you aren't technical). thats why i recommend fixing it to use winUI 3 so it is consistent.

### Rationale

it helps makes accessibility better for those who use the titlebar button (you need to cover the least common denominator, and want best practice HIG - human interface guidelines to be consistent), thats why for winUI3 apps, there are two paths, either remove the ability for that menu to appear, or redesign that control in the WinUI3 design (including fluent design guidelines)

### Scope

| Capability | Priority |
| :---------- | :------- |
| This proposal will allow developers to accomplish W | Must |
| This proposal will allow end users to accomplish X | Should |
| This proposal will allow developers to accomplish Y | Could |
| This proposal will allow end users to accomplish Z | Won't |

### Important Notes

if you don't understand for photos you click right on the titlebar where it says 'photos' and for the calculator anywhere. thats just so it can be triaged, it should consistently use the WinUI context menu as in windows 11 when right clicking stuff (not the more options design)

### Open Questions

if you want to ask any questions on how it should be designed, feel free to post those questions here so i can address them.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the titlebar menu behavior in Calculator and Photos on Windows 11, as described in the issue, and determine how WinUI 3 currently handles it. The issue names no repository files or tests; completion would require an agreed design that either removes the menu or redesigns it consistently with WinUI 3 and Fluent guidelines.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, design, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.