-
Bug
-
Resolution: Obsolete
-
Low
-
5.2
-
Severity 3 - Minor
-
Steps to reproduce:
- Create a user that has a non latin character in his name, e.g. John Stærk
- Navigate to a confluence page
- Create a new comment
- Enter as the data a mention to John Stærk
- Set a breakpoint on line 122 of EditorLinkBodyUnmarshaller, i.e.
if (StringUtils.equals(defaultAlias, linkBodyString))
- Click Save
Expected Outcome:
The default alias that contains the plain text representation of John Stærk should match the unicode representation, John Stærk. Either that, or the default alias should be the unicode representation at this point, resulting in the current representation matching.
Actual Outcome:
A blind comparison is done, which ignores whether it is unicode altogether, which interprets the values as different, and therefore determines that the body text should be stored (unnecessarily, as the default alias provides the necessary information)
This has caused a bug to surface in Confluence Dashboard All Updates CONF-28169. This does not completely fix CONF-28169 as it only addresses the ID/label variance, not whether it should be an ID or a label. More details are in STRM-2133 which was incorrectly linked.
- relates to
-
CONFSERVER-28169 All Updates replaces username with actual name in mentions only when the username has non latin characters
-
- Closed
-
- is related to
-
STRM-2133 Loading...
Thank you for your interest in this ticket. The Confluence Server and Data Center team released a major upgrade to the editor in 6.14. Due to the age of this ticket and/or lack of updates, we suspect that this issue is no longer relevant or was resolved as a result of the upgrade and are now closing this ticket.
If this issue is still a problem in your Confluence instance in version 6.15 or later, please tag me in your comment and we can reopen this ticket for review.
You can read more about the editor upgrade in the 6.14 Release Notes.
Thanks
Makisa Appleton | Senior Product Manager, Confluence Server and Data Center