Issue Summary

Interacting with inline comments located inside table cells in Edit mode causes unintended text selection (blue highlight) on adjacent or lower content and abruptly jumps/scrolls the editor to another location on the page.

Steps to Reproduce

1. Create a Confluence page with a table containing multiple rows and text content across several cells.
2. Publish the page.
3. In View mode, highlight text inside one or more table cells and add inline comments.
4. Click Edit (or press e) to enter Edit mode.
5. Click directly on the text containing an inline comment inside a table cell (or place the cursor within the <span class="inline-comment-marker ..."> boundary).

Expected Results

The cursor/caret is cleanly positioned where the user clicked, the corresponding inline comment thread highlights/aligns in the sidebar, and the editor viewport remains stable without moving.

Actual Results

1. The editor fails to collapse the caret inside the comment marker and instead creates an errant native selection range (window.getSelection()), causing the adjacent text or the cell/row below to become selected in blue.
2. The editor viewport immediately and abruptly jumps/scrolls away to the end boundary of the unintended selection.
3. This behavior reproduces exclusively when inline comments are located inside tables (comments in standard paragraphs outside tables do not trigger the issue).

No server-side exception is thrown in atlassian-confluence.log. This is a client-side JavaScript/DOM selection and viewport scrolling defect occurring in the editor canvas (TinyMCE / confluence-inline-comments plugin). When the inline-comment marker gains the "active" state inside a <td> element, event bubbling into the table selection manager triggers an unintended range selection followed by a scrollIntoView() call on the selection endpoint.

Workaround

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