Skip to content
View in the app

A better way to browse. Learn more.

Web Designer Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

HTML 5 and CSS 3

Featured Replies

It's a good post for awareness, but it's badly flawed. HTML5 is meant to improve semantics, all the person in that post has done is take a html4 layout, and wrap some html5 tags into it.

 

HTML5 isn't finished yet,so putting that into practice is a bad idea.

 

For a start

 

    <nav><ul>  
       <li class="active"><a href="#">home</a></li>  
       <li><a href="#">portfolio</a></li>  

       <li><a href="#">blog</a></li>  
       <li><a href="#">contact</a></li>  
   </ul></nav>  

 

Is utterly pointless, <nav> has been implemented to eliminate the need for the list. as <ul> is block and <li> is inline, much like <nav> and <a>.

 

<time> is a new html5 tag, but he's used <abbr> instead, which is html4 i think.

 

I think we're at the point where we can start utilising some css3 (with the exception of things like the selectors), but all i've mostly seen is people creating html4 documents, and jamming in some html5. Which is really just unnecessary code bloat.

 

Until html5 is far more widely accepted, i think people should just continue using pure html4 + microformats, as opposed to html4 mashed with a little html5.

 

Just my $0.02

Yeah, don't get your hopes up.

 

We won't be using HTML 5 for a while yet...

HTML5 isn't finished yet,so putting that into practice is a bad idea.

 

For a start

 

    <nav><ul>  
        <li class="active"><a href="#">home</a></li>  
        <li><a href="#">portfolio</a></li>  

        <li><a href="#">blog</a></li>  
        <li><a href="#">contact</a></li>  
    </ul></nav>  

 

Is utterly pointless, <nav> has been implemented to eliminate the need for the list. as <ul> is block and <li> is inline, much like <nav> and <a>.

 

<li> is a block element - not inline.

And just because <nav> is block doesn't make <ul> redundant. They have different semantic meaning. You will see W3C's examples also use a list inside the <nav> element.

 

You want to keep the list element because you have a list of links. And you wrap <nav> around that list to indicate it's the primary navigation of your site.

 

 

Until html5 is far more widely accepted, i think people should just continue using pure html4 + microformats, as opposed to html4 mashed with a little html5.

If noone starts using it until its widespread it will never be used.

 

 

 

Though, if I where still making websites for clients I wouldn't jump on HTML5 just yet. But for my own personal projects I would start playing around. Start testing it out now and you'll be well prepared for the future. It'll also give you the chance to test it out and report bugs or suggest changes.

  • Author

HTML 5 isn't finalised yet, but neither is CSS 2.1. One of the main things I like about this article is that it shows a practicle example of the current state of HTML 5. Something that did catch my attention was this part

The extras block is yet another section of our document. You might struggle for a while deciding whether an <aside> or a <section> tag would be best for this section.

I'm not entirely sure I'm looking forward to arguing with my collegues over which new element is the best for a certain situation, especially when the only difference seems to be the way that search engines or screen readers understand the whole page and there are no obvious stylistic differences.

 

Also, just to respond to bocaj's comment about <time>: <abbr> is being used to stop collisions with the chosen microformat. This certainly makes me wonder whether RDFa is a better solution that microformats

I'm not entirely sure I'm looking forward to arguing with my collegues over which new element is the best for a certain situation, especially when the only difference seems to be the way that search engines or screen readers understand the whole page and there are no obvious stylistic differences.

 

HTML5's new elements are mostly to add semantic values - not to provide new better visuals. Using semantic elements is solely there for computers to understand the content. Style isn't part of the discussion really.

It doesn't really improve semantics at the moment, you're just wrapping each element in a faux div. Google fully understands the microformats, if you use id="nav" it understands that those links are navigation elements, probably the same with. From what I've see of html5 layouts, they're all just html4 templates and a few html5 tags thrown in.

 

I think posts like that are great for increasing awareness of new html5 elements, their role, what they should be able to do, and why it's getting better.

 

But i've already had some guy insult me for using html4 because i'm 'behind the times' and i've seen more and more people putting html5 into active practice. Which is like eating an uncooked pie.

 

All people should dabble in html5 if they have the time, build a small template, play with the tags etc. but i think some posts like this, are just going to encourage people this is today's technology, when really it's still tomorrows.

 

However, used half baked, it still degrades well, but kind of misses alot of what html5 is about.

 

HTML5's new elements are mostly to add semantic values - not to provide new better visuals. Using semantic elements is solely there for computers to understand the content. Style isn't part of the discussion really

 

I think he's saying that you'll get to a point where the lines blur a bit. You have a section of your page which is related, but not directly. Should you include it as a section, or as an aside? Or could your wrap both tags around it? Is their any point?

 

Some of the tags are designed with more black and white sites in mind, sites with clear divisions between the relevancy of different content sections, but sometimes, you get your grey areas where a judgement needs to be made.

 

<aside>

Does google properly recognise these new html5 elements yet? Although, right now i don't fully trust what google officially says, not since they've started telling people that re-writing urls is bad, and they do not recommend it, even though it's something they do themselves.

</aside>

It doesn't really improve semantics at the moment, you're just wrapping each element in a faux div. Google fully understands the microformats, if you use id="nav" it understands that those links are navigation elements, probably the same with. From what I've see of html5 layouts, they're all just html4 templates and a few html5 tags thrown in.

True, it doesn't give any extra semantic value until you have something that reads it. But when HTML5 do get more support it will give better semantics.

 

 

 

But i've already had some guy insult me for using html4 because i'm 'behind the times' and i've seen more and more people putting html5 into active practice. Which is like eating an uncooked pie.

First-posters mentality. First just for the sake of being first - then gloat. Yea, that is annoying. I expect there won't be any less of them. :(

 

 

All people should dabble in html5 if they have the time, build a small template, play with the tags etc. but i think some posts like this, are just going to encourage people this is today's technology, when really it's still tomorrows.

 

However, used half baked, it still degrades well, but kind of misses alot of what html5 is about.

Yea, while it's imperative to keep up to date in web design, you have to be pragmatic about it and time adaptation.

 

 

I think he's saying that you'll get to a point where the lines blur a bit. You have a section of your page which is related, but not directly. Should you include it as a section, or as an aside? Or could your wrap both tags around it? Is their any point?

 

Some of the tags are designed with more black and white sites in mind, sites with clear divisions between the relevancy of different content sections, but sometimes, you get your grey areas where a judgement needs to be made.

If it's not directly it shouldn't be <aside>. But I see your point that some elements can be a thinker. Same as some elements in HTML4. But through use you get used to it and make quicker decisions. In any case, it won't really harm your website.

 

 

<aside>

Does google properly recognise these new html5 elements yet? Although, right now i don't fully trust what google officially says, not since they've started telling people that re-writing urls is bad, and they do not recommend it, even though it's something they do themselves.

</aside>

Their Google Wave application relies on HTML5 - so it seems they are really going for HTML5. So if they say that do recognize the elements then I see no reason to doubt it.

As for URL rewriting - I guess not everyone got the memo. ;)

  • Author

I've been looking around on the web and I've found a few more things that HTML 5 can do. Has anyone seen the HTML 5 Forms Demo in Opera 9.5+? Those are elements that should have been part of HTML to begin with -- they're a pain in the @$$ to impliment at the moment but a input type in HTML 5. I've also heard that e-mail validation is part of the spec, but I haven't seen how good it is.

 

Has anyone seen any other HTML 5 examples floating around?

I read that article as "URL rewriting is hard. We don't think you are capable of doing it right. Leave it to us."

 

 

What I think they refer to is that some people blindly rewrite each URL argument where the only difference effectively becomes transforming the ? and the & to be forward slashes / .

 

 

What they should be saying instead of "don't rewrite URLs" is "craft your URLs wisely".

bocaj:

But i've already had some guy insult me for using html4 because i'm 'behind the times' and i've seen more and more people putting html5 into active practice. Which is like eating an uncooked pie.

 

If you use <nav>...</nav>, what happens to IE5.5 or IE6? It will disrupt the page completely as the browser will ignore the div and any styles for nav so I don't see how anyone designing for the general public with old browsers can risk using HTML5 yet.

IE 5.5/6 will not style the new elements unless you add a javascript that adds the type to the DOM.

 

IE5.5 is dead and IE6 is dying. If I where still doing commercial websites I wouldn't fully support IE6 unless the client had a specific reason. Any browser older than IE7 I would feed a simpler generic stylesheet.

Though, for commercial websites I'd hold of HTML5 just a wee bit longer.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.