PUBLIC MARKS from greut with tag html5

What do we do for browsers that don't support rem units? We can specify the fall-back using px, if you don't mind users of older versions of Internet Explorer still being unable to resize the text (well, there's still page zoom in IE7 and IE8). To do so, we specify the font-size using px units first and then define it again using rem units.

html { font-size: 62.5%; } body { font-size: 14px; font-size: 1.4rem; } /* =14px */ h1 { font-size: 24px; font-size: 2.4rem; } /* =24px */

I think the HTML5 project is misguided in the same way that ES4 was. It is trying to do too much without a clear mission that defines the problems it is solving. I think the project needs a reset. I want to refocus it with the intention of producing the smallest possible standard, rather than the largest possible standard.

I would call the replacement project HTML4.2. It would be tempting to call it HTML4.1, but the current HTML standard is HTML 4.01, so the potential for confusion is too great.

Opinionated Doug is opinionated, and I think it's a good thing.

The Burst Engine is an OpenSource vector animation engine for the HTML5 Canvas Element. Burst provides similar web functionality to Flash and contains a layer based animation system like After Effects. Burst uses a very light-weight JavaScript frame, meaning your animations will download unnoticably quick and can be controlled using very simple JavaScript methods. For example: the [-] logo above is a Burst animation attached to a mouseOver event using the following code...

canvas is the next Flash or not

This specification normatively defines the fifth major version of the HTML vocabulary. It provides the details necessary for producers of HTML content to create conformant documents. By design, it does not define related APIs nor attempt to specify how consumers of HTML content are meant to process documents.

a version more usable to help you actually writing HTML5

A great way to experiment it

Comet doesn’t have to be a hack. Currently, as we saw last time, Comet relies on undocumented loopholes and workarounds, each one with some drawbacks. We can make Comet work effectively in every browser, using streaming transports on subdomains of the same second-level domain, or using script tag long polling across domains. But this leaves Comet developers implementing (and more frustratingly, debugging) several transports across several browsers. Traps are numerous and easy to stumble into.

event-source is the future of all Comet things.

"HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes.

Reminds me the old document html vs xhtml.