-
Bug
-
Resolution: Obsolete
-
Low
-
5.9.4
-
1
-
Severity 3 - Minor
-
Summary
When we create a user macro which applies CSS , then characters are not rendered as expected . eg: '>' is rendered as '>' and " (quote) is rendered as "
This causes issue with the functionality for the CSS script applied
Environment
Confluence 5.9.4
Steps to replicate
- Add a user macro call it "test"
- use the below as template
##@noparam #set($styleHtml="<style type=text/css> .wiki-content > h1 {color:red}</style>") $styleHtml
- Create a test page and add a text as heading 1
- add the user macro test
- save the page
Expected result
The text should appear as red
Actual result
The text remains unchaged and when we inspect the element with browser the applied CSS has rendered the character incorrectly > as >
[CONFSERVER-40873] CSS characters are not rendered as expected in user macros
Resolution | New: Obsolete [ 11 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Fix Version/s | New: 6.14.0 [ 83892 ] |
Workflow | Original: JAC Bug Workflow v3 [ 2886519 ] | New: CONFSERVER Bug Workflow v4 [ 2980375 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2799109 ] | New: JAC Bug Workflow v3 [ 2886519 ] |
Workflow | Original: JAC Bug Workflow [ 2716161 ] | New: JAC Bug Workflow v2 [ 2799109 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2382242 ] | New: JAC Bug Workflow [ 2716161 ] |
Status | Original: Open [ 1 ] | New: Gathering Impact [ 12072 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2274977 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2382242 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2217908 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2274977 ] |
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