Inconsistent behavior of the `r` shortcut
Summary
The r
shortcut doesn't act consistently. After page load, with no further actions, it does nothing. Focusing and unfocusing the main note text area, or clicking reply to comment, and repeating the action causes it to work as expected.
Steps to reproduce
- Open an epic (or issue, MR).
- Highlight some text in a note.
- Press
r
(with hotkeys enabled). - Notice nothing happens.
- Click on the reply to comment button.
- Enable plain text editing.
- Highlight text again and press
r
. - Notice text copied into the textarea.
Bonus:
Do the exact same thing but instead of clicking the reply to comment
button in (5), focus the new note text area. Notice that the text is copied in there instead.
Example Project
Any MR, Issue or Epic.
What is the current bug behavior?
The shortcut is unresponsive unless specific actions are taken first.
What is the expected correct behavior?
The shortcut expands the comment reply form and copies the text in there.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing)