nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why are inline resolved when revising a page?

As mentioned in the question, why the inline comments are - in some cases - resolved when revising a page? This happens randomly. In every case I have seen, the inline comments was resolved with following message:

Resolved because the text was deleted by XXX YYY yesterday at 7:15 AM

I found some bug reports from the past but I wasn't able to find any explanation why is this happening? I have a doubt that this might have something to do with inline comments added to a H1 heading but I can't be sure this is the case.

While this issue keeps existing, we need to enforce the usage of page comments instead of inline comments which is sad because the inline comments would be such a great tool for pointing out "things" from the documents.

Accepted answers

All comments

Hi @Jussi Sarén

Perhaps User A adds inline comment 1 while in edit mode (without publishing) and User B also edits and published a new version of the page in the mean time?

No, this is not the case. I'm 100% sure about this.

What I know is that the pages contain a Table of contents macro. The user is adding a new H1 header to the page and then when publishing the page inline comment added to another H1 header is being resolved.

Don't ask why, but in this case the H1 headings are within a table cell.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud