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

[Panel] Navigating dropdown items using up/down arrows keys doesn’t work correctly #1661

Closed
tillprochaska opened this issue Apr 6, 2019 · 1 comment

Comments

@tillprochaska
Copy link

commented Apr 6, 2019

Describe the bug
KDropdown highlights the active/focused item. When navigating the dropdown using the up/down arrow keys, disabled items won’t be highlighted. However, you still need to press the arrow key multiple times to skip disabled items.

To Reproduce
Steps to reproduce the behavior:

  1. Edit the home page.
  2. Click on the »Settings« dropdown.
  3. Press the down arrow key. The first item, »Rename«, is highlighted.
  4. Press the arrow key once more. The first item remains highlighted.

Expected behavior
The second enabled item (»Change status«) should be highlighted.

Screenshots

Kirby Version
3.1.2-rc.1

Console output
n/a

Desktop (please complete the following information):

  • OS: macOS Sierra
  • Browser: Chrome
  • Version: 73.0.3683.86

Smartphone (please complete the following information):
n/a

Additional context
n/a

@tillprochaska tillprochaska changed the title [Panel] Dropdown [Panel] Navigating dropdown items using up/down arrows keys doesn’t work correctly Apr 6, 2019
@distantnative distantnative added this to the 3.1.4 milestone Apr 6, 2019
@distantnative distantnative modified the milestones: 3.1.4, 3.2.0 Apr 16, 2019
@distantnative distantnative modified the milestones: 3.2.0, 3.2.1 May 3, 2019
@bastianallgeier bastianallgeier modified the milestones: 3.2.1, 3.2.2 Jul 2, 2019
@bastianallgeier bastianallgeier modified the milestones: 3.2.2, 3.2.3 Jul 10, 2019
@bastianallgeier bastianallgeier modified the milestones: 3.2.3, 3.2.4 Jul 30, 2019
@bastianallgeier bastianallgeier removed this from the 3.2.4 milestone Aug 22, 2019
@distantnative distantnative added this to the 3.2.5 milestone Sep 15, 2019
distantnative added a commit that referenced this issue Sep 15, 2019
@distantnative distantnative self-assigned this Sep 15, 2019
distantnative added a commit that referenced this issue Sep 15, 2019
bastianallgeier added a commit that referenced this issue Sep 16, 2019
@bastianallgeier

This comment has been minimized.

Copy link
Contributor

commented Sep 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.