Enter key on physical keyboard does not work on command pallette on first load (Chrome Android)

[shmatt]

Select Topic Area

Bug

Body

I'm using Chrome on Android. Not sure if this issue occurs on other environments.

When using the command pallette immediately after the first page load of the github dashboard, hitting the enter key on the physical keyboard does not trigger the action for the selected item in the list. Instead, it triggers the item that has tab focus on the underlying page

XRecorder_12072023_141806.mp4

[devrose04]

it is possible that there is a conflict between the keyboard shortcuts used by the command palette and those used by the underlying page.

One potential workaround you could try is to use the touch screen to select the desired item in the command palette instead of using the physical keyboard. Alternatively, you could try using a different browser or device to see if the issue persists.

[shmatt]

@devrose04 thank you kindly for your response.

It works as it should if I have already navigated to a new page within github.com. Just doesn't work on the first page load within github.com, so doesn't seem likely that it is a conflict with the underlying page.

I'm using a desktop environment on connected display (i.e. Samsung Dex), so touchscreen isn't an option. It will work if I use a mouse to select, but being forced to use the mouse is the issue, hence it being an accessibility concern. I can't find a way to make it work without having to resort to using the mouse. Avoiding the mouse is kind of what command palettes are for.

[cehfisher]

Hi @shmatt - thank you for providing this feedback! We wanted to follow up on this reported bug. Is this still an issue you can replicate? If it is resolved, could you please close out this issue? If it is not resolved, we can file this as an issue for the Accessibility team to review. Thank you! (cc @queenofcorgis)

[shmatt]

Hi. Yes, it is still an issue, with the behaviour not changing since I reported the issue.

Tnank you.

[cehfisher]

Thank you for the quick reply @shmatt! We will file this with our Accessibility team so that it can be reviewed and will follow-up here with any additional questions or updates. Thanks again!