Focus automatically loses when clicking on Branch name field in "Create a branch for this issue" dialog

[sverdlov93]

Select Topic Area

Bug

Feature Area

Issues

Body

Same issue as https://github.com/orgs/community/discussions/153193, which was closed.

Issue Description

When clicking the "Create a branch" link from an issue page and then clicking on the Branch name field in the "Create a branch for this issue" dialog, the focus is automatically lost immediately after gaining it. This prevents text selection or cursor movement operations (such as Ctrl+A), requiring users to click the field again to regain focus.

Steps to Reproduce

1. Open any issue page on GitHub
2. Click the "Create a branch" link
3. In the dialog that appears, click on the Branch name field
4. Focus is gained momentarily, but then automatically lost
5. Keyboard operations (such as Ctrl+A) don't work, requiring clicking the field again

Expected Behavior

After clicking the Branch name field, focus should remain on the field, allowing keyboard operations (Ctrl+A, cursor keys, etc.) to edit the text efficiently.

Environment

• Browser: Google Chrome Version 133.0.6943.142 (Official Build) (arm64)
• OS: macOS 14.5 (23F79)

I verified that the issue can be reproduced in both Firefox and Safari.
Because it occurred in each browser, I have not tested for any interference from extensions.

I also found a more detailed sequence of steps to reproduce the issue:

• It only reproduces following the original steps immediately after the browser is reloaded.
• If, on the same page, I close the dialog and then click “Create a branch” to open the dialog again, the issue does not occur.
• Following your advice and checking the DevTools Network tab, I noticed that right after a reload, when I click “Create a branch,” the two GraphQL fetches below are triggered. However, when I open it again, these queries do not appear to be called at all:

{"query":"a4b063a99c479ee7b809fa688b0234e9","variables":{"owner":"watahiki606","repo":"BiteLog"}}
{"query":"3f41ebaead699968fac6da02d1b8f377","variables":{"owner":"watahiki606","repo":"BiteLog"}}

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

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

[omerzi]

Same here

[queenofcorgis]

Thanks for reopening and adding the Bug label - it looks like your original post was closed because it was labeled Question - we'll log this to our team.

[cehfisher]

Hello @sverdlov93 - great news, the accessibility engineers were able to reproduce this issue and create a fix. Could you please re-test it on your side? Thanks!

[sverdlov93]

@cehfisher it actually happened today 7 hours ago 🫣

[cehfisher]

So sorry it isn't working for you yet! I asked the accessibility team to look into it a bit more, in case there was something a user needed to do like clear the browser cache or use a specific version of the feature, etc. In the meantime, if you have any more info to share that might be helpful, please do!

[sverdlov93]

It doesn’t happen consistently, only occasionally.
We create the issues via the REST API.
Its on github.com (saas) private organization and repositories (not self-hosted).