That's OK, I was under the impression that using it would not be backwards-compatible with previous browsers but your article says the contrary. This being said, I'm a bit afraid that this would be the first step to changing everything to HTML5 tags and attributes. I suppose that's going to happen at some point, and I'm not quite sure what would be the impact over our user base quite yet.
I just checked on Google Analytics for campus.chamilo.org and we have the following distribution of browsers (sorry for the copy-paste, look at percentage only): Internet Explorer 50 848 56,43 % 2. Chrome 18 037 20,02 % 3. Firefox 16 911 18,77 % 4. Safari 3 094 3,43 % 5. Opera 641 0,71 % 6. Opera Mini 345 0,38 % 7. BlackBerry8520 81 0,09 % 8. Mozilla Compatible Agent 39 0,04 % 9. IE with Chrome Frame 19 0,02 % 10. BlackBerry9000 15 0,02 % Inside the IE area, we have the following distribution (5.5 lives!): 8.0 38 349 75,42 % 7.0 6 837 13,45 % 3. 6.0 3 976 7,82 % 4. 9.0 1 674 3,29 % 5. 999.1 10 0,02 % 6. 5.5 2 > 0,00 % El vie, 29-04-2011 a las 17:05 +0200, Philippe Van Eerdenbrugghe escribió: > 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 _______________________________________________ Dev mailing list Dev@lists.chamilo.org http://lists.chamilo.org/listinfo/dev
