Home key has unexpected behavior in comment editor

Issue Summary

Home key has unexpected behavior in comment editor. The expected behaviour is observed in the Bitbucket versions prior to Bitbucket 7. In the later versions, this issue is observed, where the home key does not always take the cursor to the start of the same line and different behaviour is observed when the 2 lines are separated by a spacebar and the Return key.

Steps to Reproduce

1. Step 1
   Write a few sentences in the comment section of a pull request, so that it occupies 2 lines. For example:
   Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aliquam porta arcu est, ac elementum arcu tincidunt eget. Ut nulla enim, vulputate ut odio vulputate, scelerisque euismod neque. Aenean libero risus, maximus quis turpis in, fringilla eleifend est. Sed sit amet eleifend eros, laoreet vestibulum felis. Vivamus fermentum nulla nec tincidunt placerat. Mauris in eleifend nisl, a tincidunt neque. Orci varius natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.
2. Step 2
   Place the cursor at the end of the last line.

Expected Results

When you press the home key, the cursor should go to the start of the same line, whether the 2 lines are separated by a Spacebar or the Return key.

Actual Results

When we add this into the comment section of the pull request, the line starting from Lorem, appears as the first line and the line starting from Sed, appears as a second line.

• When you press the Spacebar to separate the 2 lines, the home key takes the cursor to the start of the first line, since it is taken as one line.
• When you press the Return key to separate the 2 lines, the home key takes the cursor to the start of the same line since it is taken as 2 different lines.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available