Issue Summary

Inability to paste content on certain lines within the Page's Storage Format due to residual </ac:inline-comment-marker> tags from previously deleted inline comments. This issue occurs even when no visible inline comments are present on the page.

The problem was identified during the conversion from the Legacy Editor to the New Editor, where the inline comment tags remained in the Storage Format despite the comments themselves being removed.

Steps to Reproduce

1. Access the affected page's Storage Format view.

1. Attempt to paste text/string after a line that ends with </ac:inline-comment-marker>.

1. Observe that the paste action fails on lines with the closing tag, whereas it succeeds on lines without it.

Expected Results

Text should be pastable on any line within the Page's Storage Format, regardless of the presence of </ac:inline-comment-marker> tags.

Actual Results

Pasting text fails on lines containing the </ac:inline-comment-marker> tag, indicating that leftover inline comment markers from the Legacy Editor to New Editor conversion process interfere with content editing.

Workaround

Given the nature of the issue with residual </ac:inline-comment-marker> tags in the Storage Format, a direct manual removal through the UI may not be feasible for all users. However, a solution is available through the use of the Confluence Cloud API. This method allows for a more granular approach to addressing and rectifying the issue by enabling the manipulation of page content and metadata programmatically.

To remove the residual </ac:inline-comment-marker> tags via the API, follow these steps:

1. Utilize the Confluence Cloud REST API to retrieve the current content of the affected page. Documentation for retrieving page content can be found at: Get content

1. Modify the retrieved content by removing all instances of the </ac:inline-comment-marker> tags.

1. Update the page with the cleaned content using the PUT method. Detailed instructions for updating page content via the API are available here: Update content

This approach requires some familiarity with RESTful APIs and may necessitate development resources. It is a powerful method to ensure that the page content is corrected without the risk of manual errors and can be automated for multiple pages if necessary.