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

  • I think there's challenges to this. Chiefly that HTML5, *by design*, is not XML (stackoverflow.com/.../is-html5-valid-xml)

    I would certainly support things like block-level links, and HTML5 semantics, but many other front-end developers (and IDEs that they use) have objections to the HTML5 syntax.

    HTML5 allows things like

    <table>

    <tbody>

    <tr>

    <td>text

    <td>text

    as well as <img> and <p>text<p>. IDEs and Linters throw errors at such markup. Even though it is "valid". `<div class=foo>` is also valid -- the " isn't required so long as the value is a single word.

    All of these things are "fine" for the browser because it's been built to parse these things. But almost any front-end developer's toolset will throw errors because... this looks like mistakes. Relying on the browser to know where to insert a tag has, many times, had dangerous results. I can't imagine it'd be better with Tridion.

    I would get on board with block level links, and semantic elements, and microdata. But not for any of the formatting pieces that are part of HTML5.

Comment

  • I think there's challenges to this. Chiefly that HTML5, *by design*, is not XML (stackoverflow.com/.../is-html5-valid-xml)

    I would certainly support things like block-level links, and HTML5 semantics, but many other front-end developers (and IDEs that they use) have objections to the HTML5 syntax.

    HTML5 allows things like

    <table>

    <tbody>

    <tr>

    <td>text

    <td>text

    as well as <img> and <p>text<p>. IDEs and Linters throw errors at such markup. Even though it is "valid". `<div class=foo>` is also valid -- the " isn't required so long as the value is a single word.

    All of these things are "fine" for the browser because it's been built to parse these things. But almost any front-end developer's toolset will throw errors because... this looks like mistakes. Relying on the browser to know where to insert a tag has, many times, had dangerous results. I can't imagine it'd be better with Tridion.

    I would get on board with block level links, and semantic elements, and microdata. But not for any of the formatting pieces that are part of HTML5.

Children
No Data