Resolved inline comments leave comment markers in source code and is corrupting text

[Kris Fininen]

After resolving inline comments, the inline comment markers are left in the source code. If there have been several rounds of edits with comments being placed and resolved several times, the source code becomes littered with these resolved inline comment markers.

Sometimes, the marker falls in the middle of words creating a line break in the middle of a word. This manifests in rendered pages as a space in the middle of words. This problem exports to PDF documents as well. To fix the problem, it's necessary to edit the source code and remove all old inline comment markers - in our case an extremely tedious task.

We don't remember leftover resolved comment markers being an issue until recently.

We are running Confluence 6.6.1 Server with Chrome 51.0.2704.84 m (64-bit) on Windows 7. We will be updating to Windows 10 soon.

Any ideas? Thanks.

[Simon Tost [TNG]]

I'm not sure this is still the same issue, since inline comments are now available in edit mode as well, so things have changed around them in the more recent past. But.

We have found that, depending on page size and instance performance, if you click the 'Show/Hide inline comments' button in the top bar too early, highlight markers are inserted into the page draft not only for open inline comments, but for already closed inline comments as well.
This is then persisted in the page draft, until the draft is published or discarded.

Upon publishing, Confluence does seem to clean up the storage format, so the mis-highlights should not be persistent long term. ("eventually correct" :D )

This is on a Confluence DataCenter 9.2.7.
(I couldn't find any relevant reports in the public bug tracker for this.)

[Valéria Uhljar]

Any findings here?

[Kris Fininen]

No - unfortunately not.