[Bug] Menu missing accelerators

[davidortinau]

Description

I can create a menu and use the accelerator api, however it doesn't do anything. I should be able to use this or similar to add keyboard shortcuts to menu items.

void InitMenu()
		{
			var fileMenu = new MenuBarItem { Text = "File" };
			var exitItem = new MenuFlyoutItem
			{
				Text = "Exit",
				Command = new Command((obj) =>
				{
					Application.Current.Quit();
				})
			};
			MenuItem.SetAccelerator(exitItem, Accelerator.FromString("cmd+q"));
			fileMenu.Add(exitItem);

			var locationMenu = new MenuBarItem { Text = "Location" };
			var changeItem = new MenuFlyoutItem
			{
				Text = "Change",
				Command = new Command((obj) =>
				{
					Navigation.PushAsync(new ButtonPage());
				})
			};
			locationMenu.Add(changeItem);

			var refreshItem = new MenuFlyoutItem
			{
				Text = "Refresh"
			};
			MenuItem.SetAccelerator(refreshItem, Accelerator.FromString("cmd+r"));
			locationMenu.Add(refreshItem);

			this.MenuBarItems.Add(fileMenu);
			this.MenuBarItems.Add(locationMenu);
		}

Steps to Reproduce

Add the code above to a ContentPage, run it. Note no compiler error, and no keyboard support.

Version with bug

Release Candidate 1

Last version that worked well

Unknown/Other

Affected platforms

Windows, macOS

Affected platform versions

win11

Did you find any workaround?

No response

Relevant log output

No response

[shimingsg]

verified repro with vs 17.2.0 Preview 3.0 [32313.56.main] on windows

[egvijayanand]

Pressing the Alt key or its equivalent in macOS should visually indicate the Accelerator Key mapped to that menu item, like Alt+F for the File menu.

Generally, we would achieve this like &File (Placing an ampersand sign in front of the char that would be the menu item accelerator key).

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[egvijayanand]

Hello Team,

Without accelerators for the menu items, how can the keyboard interaction happen? It's a must-have feature for desktops, both Windows and macOS. It's already a supported feature on Xamarin.Forms.

Regards,
Vijay Anand E G

[molesmoke]

@Redth Could you explain why this is only considered p2? As @egvijayanand pointed out, this is pretty much a blocker for writing a desktop app with MAUI. It seems surprising that this would get moved to the backlog.

[Redth]

We have a lot of different features and bugs that are different levels of importance to many different customers.

We are doing our best to prioritize the time and resources we have.

One of the ways we try and gauge the level of impact an issue has is activity within it (eg: comments and reactions).

We will continue to reassess which issues should be prioritized as we plan out our work.

[MartyIX]

Does anyone know about a workaround for this?

[jinxinjuan]

Verified this issue with Visual Studio Enterprise 17.6.0 Preview 3.0. Repro on windows machine with sample project.
MauiApp19.zip

[MartyIX]

(As https://github.com/dotnet/maui/issues/new?assignees=&labels=t%2Fbug&template=bug-report.yml mentions, zips are not allowed. Your sample project should be a github repo.)

[jeremy-visionaid]

Hoping to see some progress on this one! Or at least a very least workaround...
It's a blocker for accessibility, since blind/visually impaired users are going to want to access menus with keyboard accelerators.