Swtiching branch no longer puts the input field for the branch name ready to search

[mostergaard]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Repositories

Body

A change was rolled out recently on the "code" page on a repo so that when you click the "switch branches/tags" dropdown, the cursor is not put in the input search field automatically. I had this new "feature" for a little while, then it seemed to be rolled back, but now it's back again, and it's driving me crazy. I click that dropdown 100 times a day, and it's in muscle memory to click it and then I'm ready at my keyboard to type for the branch I want. But now I need to click it, and then click the input field and THEN start typing.

I post this in the "accessibility" channel because this is bad for people that are heavy keyboard users.

[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. ⭐