Touch UI Text component bug when setting 'open in a new page' option | Community
Skip to main content
Level 4
October 16, 2015
Solved

Touch UI Text component bug when setting 'open in a new page' option

  • October 16, 2015
  • 4 replies
  • 763 views

Hi,

when using the out of the box Text Touch UI component and setting the option 'open in a new page' the generated html does not have the target="_blank" attribute. It seems that the Antisamy Policy rules applied by the context 'html' used by the Sightly template strips out the target attribute. Is that a bug?

Thank you!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

If that is happening - its a bug. When you click the 'open a new page' the generated HTML should have this attribute so a new page opens. Open a ticket please. 

4 replies

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

If that is happening - its a bug. When you click the 'open a new page' the generated HTML should have this attribute so a new page opens. Open a ticket please. 

Adobe Employee
October 16, 2015

Are you also facing this in classic ui?

boser87Author
Level 4
October 16, 2015

Yes. Both Classic UI and Touch UI. I tried both "wcm/foundation/components/text" (Text - Sightly) and "foundation/components/text" (Text) components.

Adobe Employee
October 16, 2015
This could be due to xssprotection. Ideally this should work OOB. 
The fix is you may need to overlay /libs/cq/xssprotection/config.xml and add the target to the allowed attributes list for anchor tag.
For example..the below rule will allow these four target values. 
<attribute name=“target" description=“define where to open the linked document">
<literal-list>
<literal value=“_blank"/>
<literal value=“_top"/>
<literal value=“_self"/>
<literal value=“_parent"/>
</literal-list>
</attribute>