Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-7907

Multiple underscores entered into Rich Text Editor should be individually escaped

XMLWordPrintable

      When editing in Rich Text mode, a user may enter multiple underscores on either side of a sequence of non-underscore, non-space characters. The Rich Text editor does not escape all underscores, resulting in one set of underscores being incorrectly interpreted as wiki markup for italics.

      Each _ in Rich Text mode should be individually escaped with a preceding \ character.

      For example the rich text _TEXT_ is currently parsed into wiki markup as _TEXT_ and incorrectly rendered as TEXT with the text in italics. It should instead be parsed as __TEXT__ to ensure it is correctly rendered.

      Note that TEXT is escaped correctly.

            [CONFSERVER-7907] Multiple underscores entered into Rich Text Editor should be individually escaped

            Oren Held added a comment - - edited

            Even more severe, using the "Wiki Markup" tab to enter a properly, backslash-escaped underscores such as (remove the spaces) \ _ \ _ init \ _ \ _ works well,
            but then when another user edits the same page in "Rich Text" (even when changing another text), it loses the escaping and double underscores become single underscore.

            I confirmed that on Confluence 3.2 & 3.5.5

            Oren Held added a comment - - edited Even more severe, using the "Wiki Markup" tab to enter a properly, backslash-escaped underscores such as (remove the spaces) \ _ \ _ init \ _ \ _ works well, but then when another user edits the same page in "Rich Text" (even when changing another text), it loses the escaping and double underscores become single underscore. I confirmed that on Confluence 3.2 & 3.5.5

              smansour Sherif Mansour
              david.soul@atlassian.com David Soul [Atlassian]
              Affected customers:
              3 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: