Under Community Review

Update Underline Style on RTF button - Current Style is not supported by mobile Andriod

Need to update the WYSIWYG button to more modern style in Tridion RTF fields to output <u>text</u> instead of <span style=text-decoration: underline;">text</span>.
Close-up of Tridion Sites WYSIWYG toolbar with an arrow pointing to the underline button.Tridion Sites new component screen with fields for Name, Schema, and Component Content, showing 'hello' in the Design tab.
Andrew Ross
Parents

  • Thank you for your question/suggestion. As pointed out in a previous comment, the <u> tag is not intended to be used for general underlining of text. Instead, the HTML that is output by the Classic UI and Experience Space rich text editors should be used for this purpose.

    To add custom functionality to the Classic UI rich text editor, for example, a ribbon toolbar button to insert an unarticulated annotation (<u>) tag, the extension mechanism could be used.

    In Experience Space, we don't currently have extensibility support. However, a mechanism for customizing Experience Space is in active development. The rich text editor extension point, which we cannot yet commit to for the next release, should make it possible to configure the editor to output a <u> tag instead of the current markup, or to add a dedicated button for this purpose.

    As an alternative to changing the current editor behavior, you might want to consider post-processing the HTML to optimize it for specific devices/clients.

Comment

  • Thank you for your question/suggestion. As pointed out in a previous comment, the <u> tag is not intended to be used for general underlining of text. Instead, the HTML that is output by the Classic UI and Experience Space rich text editors should be used for this purpose.

    To add custom functionality to the Classic UI rich text editor, for example, a ribbon toolbar button to insert an unarticulated annotation (<u>) tag, the extension mechanism could be used.

    In Experience Space, we don't currently have extensibility support. However, a mechanism for customizing Experience Space is in active development. The rich text editor extension point, which we cannot yet commit to for the next release, should make it possible to configure the editor to output a <u> tag instead of the current markup, or to add a dedicated button for this purpose.

    As an alternative to changing the current editor behavior, you might want to consider post-processing the HTML to optimize it for specific devices/clients.

Children
No Data