Address Tag

Oh, beginning to understand better now. It's because things are a bit more complex than inline vs block in HTML5 huh? Sorry, should have kept reading, fascinating stuff.

More complex? How so ?

Am I the only one who isn't hugely impressed by anything about html5 apart from that is some of the form stuff - perhaps html5 should have just stuck to adding refinements to things like forms and support for 'video' and not tried to create too many ??semantic elements that no one is quite sure how and when to use.

From Firefox's internal default stylesheet:

address {
  display: block;
  font-style: italic;
  }

The html5 "address" element is unchanged from html4. See §6. HTML elements.

For a breakdown of element %entities, specifically %flow, see §7.1. Flow elements

Phrasing elements are the equivalents of html4's %inline elements. The rest are block elements.

I will add that I am in agreeance with Hugo that many of html5's new elements are simply cruft.

cheers,

gary

That'd be what I was looking for. Thank you Gary.

And yes, completely agree Hugo. I've been going through the list of new HTML5 tags and a lot of them I really can't see much point for. I understand that it makes the code more 'semantic' in explaining what elements are, but realistically who benefits from that? Don't get me wrong, I'm a believer in simplistic well written HTML but if the only people benefiting from some of these tags is a screen-reader whilst meanwhile a whole bunch of people end up needing the modernizer script (or equivalent) running then the benefits don't seem to outweigh the negatives?

I should also point out that I'm not talking about all the new elements here, just a few weird ones I'm finding hard to understand the new meaning of. Like why they re-introduced and etc...

Still, I'll keep reading and perhaps I'll have an epiphany.

Thanks again!

Oh the flipping debates and discussions that still ensue with all participants in a OS project responsible for drawing up new template file markup over when it's correct to use <section> or <article> become mind numbing and this is taking into consideration some very clear and authoritative examples of why & when to use that make sense when reading yet implementing just manage to not feel right. At the end of the day I do not expect to spend more than 5 minutes wondering what element I'm going to write.

http://w3fools.com/

Thanks for that Tyssen, an interesting read to be sure!

Great link tyssen, I've been shouting about w3schools for years, asking people here not to post links to it, but wasn't aware there was much support for my views that it was both inaccurate and somewhat pernicious in it's attempts to gain top page search placement.