Navigating through inline comments using the arrows breaks if navigation hits an inline comment on a text warn/info macro

Issue Summary

Given a Confluence page with a lot of content and has inline comments, navigating between the inline comments will glitch, should the following conditions are met:

1. The page contains a warn/info macro with inline comments.
2. The above macro is located at the area of page that requires the user to scroll down to view it. (The issue does not happen if the macro is located at the top of the page)
   When navigating through all the inline comments using the top and bottom arrows on the left side of the inline comment section, the navigation glitches when you hit the inline comment that is located in the warn/info macro.

In normal cases, when a user navigates through the inline comments the page will auto scroll to the text referred to by a specific inline comment. However, in the case of this bug, Confluence will not scroll to the text referred to by the inline comment in the warn/info macro. Instead Confluence, will auto scroll to the top of the page.

Steps to Reproduce

1. Create a page in Confluence with a lot of content. The content needs to be enough, so that you need to scroll down when viewing the page.
2. At the bottom of the page, add an warning macro
3. Add a text inside that macro and add some inline comments to the text.
4. Add inline comments in the various areas of the page.
5. Save the page.
6. Click on any of the text with inline comment
7. Navigate through the comments using the arrows on the top right side of the inline comment.
8. Navigate until you reach the info/warn macro's inline comment.

Expected Results

1. The browser will auto scroll to where the info/warn macro is.
2. The inline comment will be displayed at the same level where the info/warn macro is.

Actual Results

1. The browser will move to the top of the page.
2. The inline comment will still be displayed at the same level where the info/warn macro is. This means that the user can scroll down until they find the inline comment box and continue navigating from there.

Workaround

No known workaround at the moment.