[TYPO3-content-rendering] Current html5 wrapping

[Christian Hennecke]

Am 17.12.12 16:12, schrieb Thomas Skierlo:

[snip]

> Wouldn't it be much better and easier, to always use a div wrapped
> around any CType, with an additional semantic wrap inside (artice,
> section, aside, nav, joedoe). The outer div carries the uid and can be
> used for styling. The inner one is semantic only. Can be applied (and
> overridden) like a piece of cake:

I'd prefer if TYPO3 would not force additional markup on us to make the 
latest web standards work on old browsers.

> My second current problem: Unreadable setup of css_styled_content due to
> maximum compatiblity with two very different standards. Xhtml and html5.
> Wouldn't it be much easier and more intuitive to fork in the very
> beginning? If html5 ? do that, otherwise do the old stuff. This would
> increase the chance to fix responsive image issues a lot.

+1

I'm very much in favor of loading different TypoScript templates for 
XHTML and older on one side and HTML5 on the other.

Cheers,

Christian