Hi,
When is HTML5 going to take over? Or is it already in use?
| SitePoint Sponsor |
Hi,
When is HTML5 going to take over? Or is it already in use?
2020 would be a good bet. Until then, use HTML 4.01 Strict.
And that's being conservative, Christian.
Save the Internet - Use Opera | May my mother rest in peace: 1943-2009
Dan Schulz - Design Team Advisor | Follow me on Twitter
SitePoint References: HTML CSS JavaScript | Become A Guru
WordPress SEO Checklist | What WordPress Plugins Do You Use?
Web Standards Curriculum | Image Free Equal Height Columns
HTML5 official draft was already released.
You can read updates from W3.org's website.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
Draft. Not an offiical recommendation. Yet. And probably won't be for another 20 years.
Save the Internet - Use Opera | May my mother rest in peace: 1943-2009
Dan Schulz - Design Team Advisor | Follow me on Twitter
SitePoint References: HTML CSS JavaScript | Become A Guru
WordPress SEO Checklist | What WordPress Plugins Do You Use?
Web Standards Curriculum | Image Free Equal Height Columns
Which is why I said draft.Originally Posted by Dan Schulz
Draft. Not an offiical recommendation. Yet. And probably won't be for another 20 years.
There are things in the HTMl5 draft that HTML wasn't designed to do. I'm not happy with it.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
A better question might be:
When is ie6 going to die
One can only hope. I hope by the time I turn 18 and get a real job it will be dead. Probably won't though.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
Probably around the same time HTML5 becomes a full recommendation …A better question might be:
When is ie6 going to die
Birnam wood is come to Dunsinane
I would hope that HTML5 has been totally rewritten by then to get rid of all the garbage that was added - if not then we will have just replace d one problem with another.Probably around the same time HTML5 becomes a full recommendation …
There are more tags in HTML4 that need to be deprecated. The remaining tags then cover everything necessary. Most of what is suggested to be added should be done using <object>
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">
Hell ya!
The draft of HTML5 should get rid of some browsers (if only) and get rid of the depreciated crap! Noone likes them (it) anyway! It's like that smelly kid in class.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
I agree, but I won't hold my breath.
There's a couple of element types still allowed in HTML 4.01 Strict that I wouldn't mind getting rid of (big and small). I'd also like to lose a whole bunch of remaining presentational attributes, plus the event attributes, to further promote the separation of content from presentation and behaviour.
I doubt that HTML5 will get rid of any browsers overnight. HTML4 didn't.
(BTW, it's 'deprecated', not 'depreciated'.
Birnam wood is come to Dunsinane
I try to use FF3's spell check. Doesn't always work. Oh well. They should add that to the draft, getting rid of browsers I mean. I know they won't but I can always pray at night.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
I am not holding my breath for that either.
Definitely agree with all those.
I think noscript should also be deprecated or better yet instead of being only allowed in the body it should only be allowed in the head (where it would actually have some use).
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">
I use noscript in my webpages that need JS, I put a meta refresh to a page dedicated to urge people to turn on JS.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
You can't use a noscript tag with a meta tag the way HTML is currently defined because meta tags are only valid in the head and noscript is only valid in the body.
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">
It's only valid in <body> yes, but putting it in <head> with a meta refresh works just as good. Many people do it too, though I hate it not validating.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
Well, bubonic plague killed off millions of people in the 14th century, and from what I understand it still kills a few people off each year in the 21st century, so that should give you some perspective on IE6 and its lifespan....A better question might be:
When is ie6 going to die
That would be my car, house, and clunky old computer that have depreciated. And are all continuing to do so even as I type....(BTW, it's 'deprecated', not 'depreciated'.
While the value of noscript has depreciated lately, I don't think there's any reason to deprecate it.
Could you explain how you'd like to use it in the head, though? The noscript element is meant to add accessible alternative content, and since you can't have content in the head, I'm not sure I see how it would be useful.
Birnam wood is come to Dunsinane
The only thing I have actually seen where using noscript would actually be useful as an alternative to hiding the content using JavaScript (where you can be more specificas to what JavaScript features need to be supported) would be to use it around a stylesheet where the stylesheet defines those things which are only meant to be visible when JavaScript is disabled. That way you would need at most one noscript tag rather than one around each piece of content and it wouldn't be limited to blocks of content but could be used with inline content as well.While the value of noscript has depreciated lately, I don't think there's any reason to deprecate it.
Could you explain how you'd like to use it in the head, though? The noscript element is meant to add accessible alternative content, and since you can't have content in the head, I'm not sure I see how it would be useful.
You could of course achieve the same end result using just JavaScript but some browsers would then insist on temporarily displaying the "to be hidden" content until the JavaScript actually gets run. Of course there isn't any way to avoid that for where JavaScript is available but a particular feature is not.
Stephen J Chapman
javascriptexample.net, Book Reviews, follow me on Twitter
HTML Help, CSS Help, JavaScript Help, PHP/mySQL Help, blog
<input name="html5" type="text" required pattern="^$">
And you stil get the gap with the half-Javva'd browsers-- those who can support some javascripts but not all of them, or behind a selectively-blocking firewall-- so now, no JS, no noscript-- double screwed.
I recently learned the headers attribute was being dropped. Now, I'm pretty sure it's my poor table-writing skills, but I've used headers and will continue to so long as I need it. If HTML5 will force me to take a table and double its size just to get away with using scope (which I use most of the time), then I simply cannot use it (if the draft stays this way until spec).
The argument I heard was, nobody uses it, or if they do, they don't use it right.
Could've said that about seat belts in the 80's, huh. The reasoning is poor.
Bleh.
Very Not Happy. But, oh well.
Most developers don't have a proper education on everything HTML. They are bound to do something wrong. That's no reason to drop it.The argument I heard was, nobody uses it, or if they do, they don't use it right.
<font> is still used though I am sad about it.
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work
I just checked, it's for Dreambeaver etc... so it's just barely in the spec, not really fully.
Let's see, this model car uses an inappropriate safety feature, but since the company cannot change their factories over fast enough, we'll just let it be instead of making it illegal.
I thought the whole point of HTML5 was to make all browsers deal with the inevitable illegal or typo'd stuff in the same way. I feel that's kinda different from just letting some stuff stay in. Let <font> tags be an error who are handled the same way from browser to browser just as they are deprecated now in HTML4 yet all browsers still honour it.
Eh, I am truly just b****ing happily about something which I've only peeked at. I will not be using HTML5 anytime soon nor will anyone else, I just like to rant about stuff : ) I do know a lot of standardistas and smart web dudez have been working on this for a while. I just disagree with a lot of it.
Posting Permissions
Bookmarks