Writing "-->" in a string field, corrupts the content with escaped HTML characters. If you enter in the text: ‘-->’, for example in the Description field of a project, and click on the Save button, it changes to ‘-->'. What is causing the HTML special character to be converted to its corresponding HTML code? This issue is reproduced on may fields in many objects (including Risks, Ideas, Projects)
Steps to Reproduce:
Expected Result: To see this ‘-->’
Actual Result: See this ‘-->'
Sample screenshots below.
This is working as expected.
Release: All Supported
‘-->’ matches one of the XSS Patterns which can cause a cross site scripting issue and allowing this to cause security issues. ‘-->’ is a string in 'cmn_option_values’ table for option code ‘CMN.XSS.PATTERNS’ and thus it is being encoded to ‘-->' (the HTML Code)
Running the below query will list out all the XSS patterns and Clarity does a pattern match and converts the HTML character to HTML code.
In the Modern UX, where the capability to export to PDF is present, the following workaround can be used.
Use one of the escape texts below, to obtain an arrow in the PDF:
A sample screenshot below.
However, in the text box within the Product, arrows will not be noticeable.