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!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬