Posts: 2,064
Threads: 33
Joined: Nov 2005
Reputation:
37
(2011-08-09, 02:56 PM)ekerazha Wrote: You guys are creating problems that don't exist.
Just use the HTML5 doctype with HTML5 valid code. Maybe you can avoid using new tags if they cause issues to the legacy browsers, but users can use the new tags, <video> etc. if they want, because the template is HTML5 ready. And the HTML5 doctype, charset declaration etc. are designed to be backward compatible.
If you don't want the HTML5 doctype, charset declaration etc. (there isn't any good reason to avoid using them), just edit your template and replace them with the 1 km long XHTML Transitional dtd xml charset blah blah blah declarations.
The problem is that HTML 5 doesn't require a DTD, and the optional DTD doesn't specify a version. A browser which doesn't know HTML 5 may interpret the page as HTML 3.2
Posts: 8,966
Threads: 93
Joined: Oct 2007
Reputation:
99
(2011-08-09, 02:56 PM)ekerazha Wrote: You guys are creating problems that don't exist.
If you don't want the HTML5 doctype, charset declaration etc. (there isn't any good reason to avoid using them), just edit your template and replace them with the 1 km long XHTML Transitional dtd xml charset blah blah blah declarations.
The same can be said about you. You can just as easily switch to html5...
Posts: 89
Threads: 6
Joined: Mar 2011
Reputation:
3
2011-08-09, 05:21 PM
(This post was last modified: 2011-08-09, 05:31 PM by ekerazha.)
(2011-08-09, 03:17 PM)laie_techie Wrote: The problem is that HTML 5 doesn't require a DTD, and the optional DTD doesn't specify a version. A browser which doesn't know HTML 5 may interpret the page as HTML 3.2
It doesn't work that way. HTML browsers are not validators.
Read here: http://en.wikipedia.org/wiki/Quirks_mode...ment_types
The HTML5 doctype triggers the standard mode/almost standard mode on most current and legacy browsers, Netscape Navigator 6 seems to be an exception (NN6? Really?  ). It was chosen because of this.
(2011-08-09, 04:36 PM)Alex Smith Wrote: The same can be said about you. You can just as easily switch to html5...
The point is that there are no good reasons to keep a legacy doctype, while there are good reasons to use the HTML5 doctype by default (plugins could use HTML5 features, being the template HTML5 ready).
Posts: 8,966
Threads: 93
Joined: Oct 2007
Reputation:
99
2011-08-09, 06:26 PM
(This post was last modified: 2011-08-09, 06:26 PM by Alex Smith.)
And, what good reason is there to switch to html5 doctype? It changes nothing about the page it self. And, one of the big things about HTML5 is not dropping support for anything so thus legacy is still considered HTML5 compliant.
And, once again there is nothing that's going to stop you from using HTML5 on your site.
Don't get me wrong I'm a big fan of HTML5 but I don't think it should be the default yet.
Posts: 89
Threads: 6
Joined: Mar 2011
Reputation:
3
2011-08-09, 06:43 PM
(This post was last modified: 2011-08-09, 06:44 PM by ekerazha.)
I've already replied to this...
i.e. plugins could use HTML5 features, being the template HTML5 ready
Posts: 8,966
Threads: 93
Joined: Oct 2007
Reputation:
99
(2011-08-09, 06:43 PM)ekerazha Wrote: I've already replied to this...
i.e. plugins could use HTML5 features, being the template HTML5 ready
The world isn't HTML5 ready yet though. And, I'm sure it would be to hard to modify a plugins template edits to make them html5 complaint as well.
Posts: 89
Threads: 6
Joined: Mar 2011
Reputation:
3
This is the reason why the HTML5 doctype, charset declaration etc. are backward compatible. If you want you also add HTML5-only features, otherwise you don't add them. Simple.
Posts: 1,069
Threads: 37
Joined: May 2009
Reputation:
48
(2011-08-09, 06:26 PM)Alex Smith Wrote: And, what good reason is there to switch to html5 doctype? It changes nothing about the page it self. And, one of the big things about HTML5 is not dropping support for anything so thus legacy is still considered HTML5 compliant. It's shorter and is valid/compatible with almost every single browser. There is no reason not to use it unless you just really want extra data being sent every page view.
(2011-08-09, 06:26 PM)Alex Smith Wrote: And, once again there is nothing that's going to stop you from using HTML5 on your site. Right now HTML5 is ready to be used, and needs to be used with vigor. There is nothing wrong with you continuing to use HTML4 on your site, however, it makes sense that with the current timeframe of MyBB 2.0's release, HTML5 is the best plan of action.
(2011-08-09, 07:00 PM)Alex Smith Wrote: The world isn't HTML5 ready yet though. Why? As it's been said before, a lot of the features and semantic tags in HTML5 are fully compatible with browsers in use today, save for some edge cases that are easily circumvented.
There has always been a struggle with cross-browser support; existing, accepted technology in the HTML4 and CSS2 specifications need to be worked with to provide support for major browsers even today. Holding back now because something might go wrong is fallacious and does nothing to solve the problem.
I suggest you read through the entirety of Dive Into HTML5.
Posts: 8,966
Threads: 93
Joined: Oct 2007
Reputation:
99
To bad IE8 is still the most use browser in the world and it doesn't support most of HTML5 features. And, I've read a number of HTML5 books and know the subject well.
http://caniuse.com/#cats=HTML5 - Shows how well different browsers support featuers.
http://www.w3counter.com/globalstats.php and http://gs.statcounter.com/#browser_versi...201107-bar
Show us what browsers are being used. As you can see somewhere around 20% of the world is still using IE8 which only supports 20% of HTML5...
Posts: 1,069
Threads: 37
Joined: May 2009
Reputation:
48
(2011-08-10, 01:04 AM)Alex Smith Wrote: To bad IE8 is still the most use browser in the world and it doesn't support most of HTML5 features. And, I've read a number of HTML5 books and know the subject well.
http://caniuse.com/#cats=HTML5 - Shows how well different browsers support featuers.
http://www.w3counter.com/globalstats.php and http://gs.statcounter.com/#browser_versi...201107-bar
Show us what browsers are being used. As you can see somewhere around 20% of the world is still using IE8 which only supports 20% of HTML5...
Unfortunately, what you're citing has little to do with suggestions of using the HTML5 DOCTYPE, short stylesheet declarations, semantic elements (might require a little workaround for IE), and the like.
If MyBB 2.0 wants to be up-to-date and a serious contender upon release, HTML5 needs to be recognized and in use. I'm not saying use all the features HTML5 has to offer, but as of right now, use those that are supported and do work well.
|
