Cannot Add Inline Comment to Plain Text using Chrome

[Steve]

When I want to add an inline comment to plain text I get the following error message: “We can’t add your inline comment; the section you
highlighted may contain a macro or user mention. Try highlighting plain text.”
It is definitely plain text and the storage format looks ok.

The error is non-deterministic and occurs only when using Chrome.

I see the following error in the JS console:
POST https://XXXXXX.com/rest/inlinecomments/1.0/comments 412 (Precondition Failed)
XMLHttpRequest.send @ batch.js?analytics-e…r-enabled=true:9271

Thanks in advance.

Best regards,
Steve Strauch

[Shannon Spaniol · Accepted solution]

Steve,

Can you tell us how many words you selected when you attempted the inline comment? Was the selection in another language, and are you able to leave inline comments on other sections?

Secondly, what version of Confluence are you using?

Thank you!

Shannon

[Steve]

@Shannon Spaniol thanks for your answer.
I selected the first word of a bullet point that is in bold. The bullet point contains more text.

The Confluence Version is 6.6.3.

Thanks.

Cheers,
Steve

[Shannon Spaniol]

Thank you Steve,

I was finding the issue was happening with short two-letter words as well, so I wanted to verify.

It appears that you have run into a bug that has since been resolved in Confluence 6.12.0:

• CONFSERVER-40019 Cannot add Inline comment (plain text)

When you're ready to upgrade, you can go straight to 6.12.0 and your issue should be resolved.

If you have any questions about that process, feel free to let us know.

Regards,

Shannon

[Steve]

Hi @Shannon Spaniol, 

thank you for your support.
I marked a five-letter word when I got the error message.

You are right. Thanks for pointing to the bug report.

Best regards,
Steve

[Shannon Spaniol]

Steve,

No problem at all! Happy to be able to connect you to the proper bug report.

Take care, and kind regards,

Shannon

[Runtastic GmbH]

Hi Shannon,

We are already on confluence 7.11.1 version but we still have this issue.