[TYPO3-BLE] BLE, core and HTML5

[Patrick Broens]

Hi,

> We must be turned toward the future, I agree.

Right

> What part of HTML 5 will be problematic in your eyes? I am assuming
> Structural tags
> such as <header>, <nav>, <article>, <section>, <aside>, <footer> which
> can't be styled with CSS in IE7. Or even worse, will not be rendered at
> all!?

Structural tags will get a big problem for all CMS's. A CMS can't decide
what is an article, section or aside. That's up to the editor. And
multiple cObj's can make one article, so TYPO3 needs to have some kind
of a container element.

The problem I was talking about is for instance:
<figure>
	<img>
	<figcaption>
<figure>

I've made a lot of changes recently to the output of image blocks to get
rid of all these inline width styles. These were for keeping the caption
within the width of the image. I now use a table with a caption tag
inside this table to get this done (HTML4, XHTML) No width involved
anymore. Of course the table is only there when a caption is available ;-)

For HTML5 I want to have the markup as shown above. To have the
figcaption within the width of the image, you need some CSS2.1 to get
this right. The <figure> needs to be display:table. The img and
figcaption need to be display:table-row or display:table-cell. And these
display properties are not supported by IE7.

> Could we have a fall back solution to conciliate both worlds?

I just had a Skype meeting with Ingmar, Ollie and Benni. We all agreed
we want to have proper HTML5 output without any fallback.

When somebody is using the config.doctype=html5 and still wants support
for older browsers, it should enable Modernizr, which is shipped with
the TYPO3 core since 4.5 (didn't know that ;-)

Patrick


> E.g.
> http://www.webdesign-gm.co.uk/news/web-design/html-5-tutorial-workarounds.html
> 
> http://sroucheray.org/blog/2009/10/html5-support-workarounds-and-fallbacks/#html5-tags
> 
> 
> 
>> So my questions to you are:
>> What is more important here? Older browser support or proper HTML5
>> output with CSS2+? We have always focused on the support for older
>> browsers, but this stops the progress of TYPO3 regarding the use of
>> HTML5. Do we tell our clients when they use HTML5 in TYPO3, older
>> browsers are not supported, or do we adapt the HTML5 output, so it still
>> will work in older browsers, which means the output is not using HTML5
>> at its full glory? Where do we draw a line?
> 
> We need also to think of mobile devices which will become more and more
> common. But I would be more confident as they mostly rely on modern
> rendering engines.
> 
> Fb.