Idea Delivered

Support for HTML5 is available now in the RTF-editor in Experience Space version 9.5.

Support HTML5 in Rich Text field.

There was a discussion about "HTML5 in Rich Text field" in the link below. "HTML5 in Rich Text field" is not supported.
https://tridion.stackexchange.com/questions/16779/let-sdl-web-8-rich-text-field-support-html-5

We have a request that it should be supported.

Yoshihisa Komai
Parents

  • :

    Thanks for the vote. Votes for any given idea help show community interest in an idea, but don't necessarily guarantee implementation nor timeline since Product Management and Development needs to consider the product fit, business impact, and feasibility for any given idea.

    For ways to improve this or other ideas please see community.sdl.com/.../.

    :

    Giving users the ability to manage the output of source content could introduce a few challenges including the ability to break a site's markup with the incorrect choice, the need for additional template logic to handle both scenarios, and most importantly, an inability to share content between sites.

    Perhaps adjusting this format during publishing would be a better approach in case of transitions between formats.

    Here's my own view on custom XML and attributes in the rich text format area:

    www.tridiondeveloper.com/rich-text-format-area-css-classes-vs-custom-xml-nodes

    More tangible use cases could help make this request better.

    : If possible, I'd prefer a single way to control the allowed markup in a rich text field which might even influence the visible RTF controls. Ideally we wouldn't need XSLT to adjust Component source.

Comment

  • :

    Thanks for the vote. Votes for any given idea help show community interest in an idea, but don't necessarily guarantee implementation nor timeline since Product Management and Development needs to consider the product fit, business impact, and feasibility for any given idea.

    For ways to improve this or other ideas please see community.sdl.com/.../.

    :

    Giving users the ability to manage the output of source content could introduce a few challenges including the ability to break a site's markup with the incorrect choice, the need for additional template logic to handle both scenarios, and most importantly, an inability to share content between sites.

    Perhaps adjusting this format during publishing would be a better approach in case of transitions between formats.

    Here's my own view on custom XML and attributes in the rich text format area:

    www.tridiondeveloper.com/rich-text-format-area-css-classes-vs-custom-xml-nodes

    More tangible use cases could help make this request better.

    : If possible, I'd prefer a single way to control the allowed markup in a rich text field which might even influence the visible RTF controls. Ideally we wouldn't need XSLT to adjust Component source.

Children
No Data