In GitHub PRs, "Quote reply" is not keyboard accessible.

[daniel-montalvo]

Select Topic Area

Bug

Body

To replicate.

• Open a GitHub issue or PR with a comment.
• Select the "More options" button, and then arrow down until you get to "Quote reply".
• Press Enter.

Expected behavior: The popup closes and the cursor is on the edit field with the contents of the previous comment preceeded by greater signs ">".

Obtained behavior: The popup closes and focus goes back to the "More options" button. Either the mouse or screen reader mouse-click simulation techniques are required to activate "Quote reply".

[patrickhlauke]

Confirming that I can see the same bug (strangely, the "Quote reply" seems to work fine here in discussions, but not on issues)

[queenofcorgis]

Thank you for this report. It has been logged internally.

Any additional members who are experiencing the same situation, please comment to share or upvote it.

We appreciate you contributing and continuing to support other users in the GitHub Community Discussions.

[daniel-montalvo]

Hi @queenofcorgis

Thanks for answering back. Do we have an idea as to when this could be addressed?

[cehfisher]

Hello @daniel-montalvo - thank you for taking the time to provide this feedback! Our Accessibility team is actively working on this issue. We will follow-up here with any additional questions or updates when we have them. Thanks again!

[cehfisher]

Hi @daniel-montalvo - there were some recent updates to the component you had issues with previously. Could you re-test things out on your end to see if they have been resolved for you? Thanks so much!

[patrickhlauke]

@cehfisher sadly, from my testing just now, "Quote reply" still doesn't work when you try to activate it with a keyboard (all other commands do work, this is the odd one out)

EDIT: actually, turns out that it works in issues (with the new changes to issues), but not pull requests (which still use the old structure/component)

[cehfisher]

Thanks for the review @patrickhlauke! We have updated the internal tracking issue with this information. We will follow-up with any updates soon.

[daniel-montalvo]

Thanks @patrickhlauke

Yes, it is not working on my side either.

there are other nice improvements to issues that are not making their way into the PR views, like each issue being an h3. It would be great it the issues and PR views could be harmonized.