Laibcoms wrote:

...

These new elements will replace our existing "divs", here's an example code:

...
      <script>
         document.createElement('article');
         document.createElement('footer');
         document.createElement('header');
         document.createElement('nav');
         document.createElement('section');
      </script>
...

So what happens when scripting is either blocked or beyond the capacity of the visitor's surfing tool?

Laibcoms wrote:

...

If you try that out, of course it will look plain, because we haven't applied any style to it yet. So now, instead of say, <div style="post posts">, we'll have <article>.

...

er... I don't know of any skins that do <div style="post posts">. Typically the code is this:

<div id="<?php $Item->anchor_id() ?>" class="bPost bPost<?php $Item->status_raw() ?>" lang="<?php $Item->lang() ?>">

resulting in, more or less <div style="bPost bPostpublished"> (ignoring the ID and lang bits obviously). So how does having <article> let me style posts differently for published vs protected vs private?

-------------------

Nice of 'em to drive everything to XHTML then decide to humor themselves with HTML5 though. Personally I'll learn from the past and not follow where they think we should all go untill and unless I personally see a need to. If b2evo wants to, well, the same thing applies. If and when I see a need to humor them, which will pretty much mean when XHTML 1.0 Trans completely fails in major browsers, I'll think about whatever "standard of the month" they're pushing.

EdB wrote:

Laibcoms wrote:

...

These new elements will replace our existing "divs", here's an example code:

...
      <script>
         document.createElement('article');
         document.createElement('footer');
         document.createElement('header');
         document.createElement('nav');
         document.createElement('section');
      </script>
...

So what happens when scripting is either blocked or beyond the capacity of the visitor's surfing tool?

Good point. For IE users, that will be a disaster, and sadly IE still has the majority share. Although for my sites at least, there are so few (as in "few") IE visitors who have scripting disabled, based on analytics reports.

EdB wrote:

Laibcoms wrote:

...

If you try that out, of course it will look plain, because we haven't applied any style to it yet. So now, instead of say, <div style="post posts">, we'll have <article>.

...

er... I don't know of any skins that do <div style="post posts">. Typically the code is this:

<div id="<?php $Item->anchor_id() ?>" class="bPost bPost<?php $Item->status_raw() ?>" lang="<?php $Item->lang() ?>">

resulting in, more or less <div style="bPost bPostpublished"> (ignoring the ID and lang bits obviously). So how does having <article> let me style posts differently for published vs protected vs private?

It was meant as an example not as a direct quote of b2evolution :p

EdB wrote:

-------------------

Nice of 'em to drive everything to XHTML then decide to humor themselves with HTML5 though. Personally I'll learn from the past and not follow where they think we should all go untill and unless I personally see a need to. If b2evo wants to, well, the same thing applies. If and when I see a need to humor them, which will pretty much mean when XHTML 1.0 Trans completely fails in major browsers, I'll think about whatever "standard of the month" they're pushing.

I'll quote some from their FAQs:

WHATWG

The WHATWG is a growing community of people interested in evolving the Web. It focuses primarily on the development of HTML and APIs needed for Web applications.

The WHATWG was founded by individuals of Apple, the Mozilla Foundation, and Opera Software in 2004, after a W3C workshop. Apple, Mozilla and Opera were becoming increasingly concerned about the W3C’s direction with XHTML, lack of interest in HTML and apparent disregard for the needs of real-world authors. So, in response, these organisations set out with a mission to address these concerns and the Web Hypertext Application Technology Working Group was born.

What is HTML5

HTML 5 is a new version of HTML 4.01 and XHTML 1.0 addressing many of the issues of those specifications while at the same time enhancing (X)HTML to more adequately address Web applications. Besides defining a markup language that can be written in both HTML (HTML5) and XML (XHTML5) it also defines many APIs that form the basis of the Web architecture. These APIs are known to some as "DOM Level 0" and have never been documented. Yet they are extremely important for browser vendors to support existing Web content and for authors to be able to build Web applications.

How are pre-HTML5 documents parsed?

All documents with a text/html media type (that is, including those without or with an HTML 2.0, HTML 3.2, HTML 4.01, or XHTML 1.0 DOCTYPE) will be parsed using the same parser algorithm as defined by HTML5. This matches what Web browsers have done for HTML documents so far and keeps code complexity down. That in turn is good for security, maintainability, and in general keeping the amount of bugs down. The HTML syntax of HTML5 therefore does not require a new parser and documents with an HTML 4.01 DOCTYPE for example will be parsed using the HTML5 parser.

Validators are allowed to have different code paths for previous levels of HTML.

For more info:
http://wiki.whatwg.org/wiki/FAQ
http://wiki.whatwg.org/wiki/HTML_vs._XHTML

Again, I only mentioned a few, it isn't a representation of HTML5 as a whole. After reading the latest spec a few days ago, I like where it is going compared to where W3C brought the development - ie dropping HTML in favor of XHTML when the majority of the world uses plain HTML.

^_^