HTML 5 Specifications & Implementations Officially Released

  • (3 Pages)
  • +
  • 1
  • 2
  • 3

37 Replies - 9262 Views - Last Post: 21 June 2011 - 08:49 AM

#31 RudiVisser  Icon User is offline

  • .. does not guess solutions
  • member icon

Reputation: 1004
  • View blog
  • Posts: 3,562
  • Joined: 05-June 09

Re: HTML 5 Specifications & Implementations Officially Released

Posted 21 July 2009 - 09:46 AM

and what about when we want to define our own elements/DTD?

EDIT: Or can they still go in the doctype def as usual? Just *allowed* to be omitted?

This post has been edited by MageUK: 21 July 2009 - 09:51 AM

Was This Post Helpful? 0
  • +
  • -

#32 Nykc  Icon User is offline

  • Gentleman of Leisure
  • member icon

Reputation: 729
  • View blog
  • Posts: 8,642
  • Joined: 14-September 07

Re: HTML 5 Specifications & Implementations Officially Released

Posted 21 July 2009 - 10:44 AM

You can still define your own elements/DTD definition.
Was This Post Helpful? 0
  • +
  • -

#33 CodyD  Icon User is offline

  • D.I.C Head

Reputation: 4
  • View blog
  • Posts: 75
  • Joined: 19-August 10

Re: HTML 5 Specifications & Implementations Officially Released

Posted 28 March 2011 - 03:36 PM

Does this mean HTML5 is fully released? Because they said it wouldn't be fully released until 2025 o.O
Was This Post Helpful? 0
  • +
  • -

#34 Arbitrator  Icon User is offline

  • D.I.C Addict
  • member icon

Reputation: 51
  • View blog
  • Posts: 530
  • Joined: 26-January 05

Re: HTML 5 Specifications & Implementations Officially Released

Posted 28 March 2011 - 10:24 PM

View PostCodyD, on 28 March 2011 - 05:36 PM, said:

Does this mean HTML5 is fully released? Because they said it wouldn't be fully released until 2025 o.O

2022 was the estimated date that HTML5 would reach "W3C Recommendation" status. That status requires that the spec be finished and that there are two complete implementations that are compatible with one another. Note that the process to reach W3C Recommendation is a lot more strict than when HTML4 was published; in particular, you need to write tests to make sure that browsers support the spec correctly and that there aren't holes in the spec. This is why specs like CSS2.1 are still not W3C Recommendations despite having been begun back in 1998 (via CSS2.0).

As for the actual date, the WHATWG basically says that "it'll get done when it gets done". See http://wiki.whatwg.o..._be_finished.3F.
Was This Post Helpful? 1
  • +
  • -

#35 skorned  Icon User is offline

  • New D.I.C Head

Reputation: 13
  • View blog
  • Posts: 41
  • Joined: 30-August 08

Re: HTML 5 Specifications & Implementations Officially Released

Posted 30 May 2011 - 10:12 PM

View Postnoorahmad, on 08 July 2009 - 11:08 PM, said:

old browsers supports these new tags?


I think a lot of the more semantic tags that have no actual functionality are quite backwards compatible. For example, when the old IEs encounter tags like <nav> or <section> that they are not familiar with, they will just be treated / rendered as divs, which is what they essentially are. The more functional tags however, such as canvas, may not.
Was This Post Helpful? 0
  • +
  • -

#36 Arbitrator  Icon User is offline

  • D.I.C Addict
  • member icon

Reputation: 51
  • View blog
  • Posts: 530
  • Joined: 26-January 05

Re: HTML 5 Specifications & Implementations Officially Released

Posted 31 May 2011 - 01:35 AM

View Postskorned, on 31 May 2011 - 12:12 AM, said:

I think a lot of the more semantic tags that have no actual functionality are quite backwards compatible. For example, when the old IEs encounter tags like <nav> or <section> that they are not familiar with, they will just be treated / rendered as divs, which is what they essentially are.

Actually, they won't. In older versions of IE, element tags such as <nav> and </nav> get treated as if they were two distinct void elements (i.e., nav and /nav elements with no content).

In browsers that recognize the tags as expected (i.e., as one element), the behavior is still not that of a div (block-level) element, but of a span (inline) element.
Was This Post Helpful? 0
  • +
  • -

#37 hockey97  Icon User is offline

  • D.I.C Regular

Reputation: -77
  • View blog
  • Posts: 300
  • Joined: 25-September 08

Re: HTML 5 Specifications & Implementations Officially Released

Posted 20 June 2011 - 05:33 AM

I could careless about html5. I rather be looking for new web browsers that follow a standard. I hope and wish that we will have once clear easy to learn standard so that the webpage will look exactly the same and function exactly the same regardless what browser our clients uses.

This is what I am looking forward. They better get their act together.
Was This Post Helpful? 0
  • +
  • -

#38 Dormilich  Icon User is online

  • 痛覚残留
  • member icon

Reputation: 3541
  • View blog
  • Posts: 10,256
  • Joined: 08-June 10

Re: HTML 5 Specifications & Implementations Officially Released

Posted 21 June 2011 - 08:49 AM

View PostNykc, on 21 July 2009 - 04:46 PM, said:

To be honest the more I dig into HTML 5, the more I like it.

<!DOCTYPE html>

<!-- So much better than having to type -->

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


thatís just a bogus DTD to trigger standards mode. (and thatís why XHTML5 explicitly must not use it).
Was This Post Helpful? 0
  • +
  • -

  • (3 Pages)
  • +
  • 1
  • 2
  • 3