First of all sorry for all the types errors in my previous message :s.
I don't understand what compatibility issues it might create if we just
change the doctype. Of course the core shouldn't use any of the html5
possibilities without providing a graceful degradation to xhtml but
changing the doctype only shouldn't break anything I guess since xhtml
is valid html5.
On the other hand, sending a doctype of html5 would allow optional-apps
to use html5 new features.
Can you tell me what kind of browsers would reject <!DOCTYPE HTML> since
even google uses it ?
Systho.
For info : My question came from reading this post :
http://www.webmaster-source.com/2010/11/29/its-safe-to-use-the-html5-doctype-today/
Le 29/04/2011 16:51, Yannick Warnier a écrit :
Hi all,
does anyone see a problem if we change the Header#tiHTml to produce a
html5 doctype insetad of an xhtml ?
Hi Philippe,
I do. For reverse-compatibility with old browsers, there should be an
way to configure the portal to ask for XHTML. Is there a way whereby,
instead of setting it straight, you can define a configuration parameter
in a special "Legacy support" section of the settings page?
Yannick
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
