[OPEN] Pressing G in speedgrader shortcuts does not work with checkpointed discussions

Engineers are currently investigating the issue.
Description
When Full Discussion Context is shown in speedgrader, the following Speedgrader shortcuts no longer work
- c: should shift focus to comment box in right pane, this does not happen because focus is set to whichever reply is highlighted (in discussion iframe)
- g: should shift focus to grade input, this does not happen for checkpointed discussions since we replace the grade input to reply to topic and reply to entry grade inputs
- j: should change to next student, does not work because focus is set to whichever reply is highlighted (in discussion iframe) (do not work on this, will be handled in EGG-1078)
- k: should change to previous student, does not work because focus is set to whichever reply is highlighted (in discussion iframe) (do not work on this, will be handled in EGG-1078)
- r: should jump focus to rubric section in right pane (do not work on this, will be handled in EGG-1078)
Expected Behavior
for all: if a discussion shortcut collides with a speedgrader shortcut, change the discussion shortcut
- c: should shift focus to comment box in right pane, to do this, we have to listen for “c“ in discussions, then send it up to speedgrader handler for “c“ .
- g: should shift focus to grade input in right pane (if not checkpointed), or reply to topic input (if checkpointed), to do this, we have to listen for “g“ in discussions, then send it up to speedgrader handler for “g“ .
- j: (do not work on this, will be handled in EGG-1078)
- k: (do not work on this, will be handled in EGG-1078)
- r: do not work on this (will be handled in EGG-1078)
Workaround
No workaround exists at this time.
Steps to Reproduce
Prerequisites: Have a course with a checkpointed discussion or a regular graded discussion
- visit speedgrader
- switch to full discussion context
- notice none of the speedgrader shortcuts work after autofocus goes to first discussion reply
Additional Info
EGG-1127
Known issues indicate notable behaviors that have been escalated to the Canvas engineering team. Known issues are not a guarantee for an immediate resolution. This document is for informational purposes only and does not replace the Support process. If you are encountering the behavior outlined in this document, please ensure you have submitted a Support case (per your institution's escalation process) so Canvas Support can adequately gauge the overall customer impact and prioritize appropriately.