Changes between Version 1 and Version 2 of Ticket #3402


Ignore:
Timestamp:
12/22/2015 11:47:05 AM (4 years ago)
Author:
kzar
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3402 – Description

    v1 v2  
    11=== Background === 
    2 Our CMS allows some inline HTML tags (`a`, `em`, `sup`, `strong`, `code`, `span`) inside of translatable strings. These tags can even be nested. 
     2Our CMS allows some inline HTML tags (`a`, `em`, `sup`, `strong`, `code`, `span`) inside of translatable strings, they can even be nested. 
    33 
    44It appears that this does not work correctly when an `<a>` tag (Or perhaps any tag with an attribute?) is nested inside of another inline tag. In that case the containing tag ends up being HTML escaped. 
    55 
    66=== What to change === 
    7 Ensure that links inside of inline tags do not cause the the inline tag to be escaped. With example `Hello world <sup><a href="#ref">1</a></sup>`, the opening and closing `sup` tags should not be escaped. 
     7Ensure that links inside of inline tags do not cause the the inline tag to be escaped. With the example string `Hello world <sup><a href="#ref">1</a></sup>` the opening and closing `sup` tags should not be escaped.