Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Gallery][All platforms]Menubar-Control key information is missing in opened flyouts for 'Menubar with keyboard accelerators' option #13813

Open
sakshi173 opened this issue Sep 26, 2023 · 1 comment
Labels
area/canary 🐤 Categorizes an issue or PR as relevant to canary testing area/porting 🖨️ Categorizes an issue or PR as relevant for porting of WinUI code difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/bug Something isn't working platform/all Categorizes an issue or PR as relevant to the all platforms project/input ⌨️ Categorizes an issue or PR as relevant to input (Button, CheckBox, Toggle, Scroll, Map, Numeric,...) project/keyboard ⌨️ Categories and issue or PR as relevant to keyboard input or keyboard accelerators.

Comments

@sakshi173
Copy link

Current behavior

menubar short key issue

Expected behavior

menubar short key correct

How to reproduce it (as minimally and precisely as possible)

  1. Open Uno Gallery APP .
  2. Click/tap Burger Menu on the left top right.
  3. Click/tap "Menubar" from the "Component" list.
  4. Go to 'Menubar with keyboard accelerators' option.
  5. Click on 'File' Flyout.
  6. Notice that Control key information is missing in opened flyouts.

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

WebAssembly, Android, iOS, Skia (GTK on Linux/macOS/Windows)

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

@sakshi173 sakshi173 added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification platform/all Categorizes an issue or PR as relevant to the all platforms area/canary 🐤 Categorizes an issue or PR as relevant to canary testing difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Sep 26, 2023
@MartinZikmund MartinZikmund added project/input ⌨️ Categorizes an issue or PR as relevant to input (Button, CheckBox, Toggle, Scroll, Map, Numeric,...) area/porting 🖨️ Categorizes an issue or PR as relevant for porting of WinUI code difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI and removed triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Oct 25, 2023
@MartinZikmund
Copy link
Member

Probably because of our lack of keyboard accelerator support in general (#13341)

@MartinZikmund MartinZikmund added the project/keyboard ⌨️ Categories and issue or PR as relevant to keyboard input or keyboard accelerators. label Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/canary 🐤 Categorizes an issue or PR as relevant to canary testing area/porting 🖨️ Categorizes an issue or PR as relevant for porting of WinUI code difficulty/medium 🤔 Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI kind/bug Something isn't working platform/all Categorizes an issue or PR as relevant to the all platforms project/input ⌨️ Categorizes an issue or PR as relevant to input (Button, CheckBox, Toggle, Scroll, Map, Numeric,...) project/keyboard ⌨️ Categories and issue or PR as relevant to keyboard input or keyboard accelerators.
Projects
None yet
Development

No branches or pull requests

2 participants