PUBLIC MARKS with tag html5

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.

Simon Willison pointed out the part of the HTML 5 spec that discusses a way to add attributes to HTML elements for your own needs via data-.

HTML5 Overview

# [10:43] Hixie: karl of course totally misunderstood what i meant by "doesn't work", as usual

I would _not_ support this position if I thought that most people who used this STYLE attribute would understand it. In HTML 5.0, when everyone understands exactly what the Web is, we can make it easier to get at.

Note that the full range of _relative_ sizes specified by the author is preserved in this scheme, which may simply be necessary to differentiate the 12 levels of heading in, say, HTML 5.

_BUT_, they can be private techniques which won't break current and future WWW clients. Otherwise, each new data element will require not only the discussion/consensus cycle, but also the implementation cycle for each Web browser or server out there.

HTML Evolution Considered Harmful - And a Path Out Version: 1.0 Brian Behlendorf, [log in to unmask] 1 October 1995

The HTML WG has several times expressed a strong preference that HTML be officially extended only by standards-track "versions", not by registered extensions. This is the reason why proposed individual feature extensions are being handled with experimental RFCs, rather than as standards-track ones. The responsible Applications Area Director would prefer that IANA start a registry of this type only in coordination with that WG, lest the registration mechanism become an alternative to normal IETF processing.

No consensus on the versioning problem

Math in HTML (was: Re: HTML4 (or 3.1))

An Extension Mechanism for HTML

WebKit had a number of minor parsing bugs that Acid 3 targeted. [...] We have updated our parser to be much closer to the HTML5-specified parsing rules.

The <canvas> element supports drawing text on it via experimental Mozilla-specific APIs.

WebKit has also never parsed DOCTYPEs before. I re-wrote WebKit’s DOCTYPE parsing to match the HTML5 specification, and so now if you put a DOCTYPE into your page it will be present in the DOM. In addition many bugs centered around proper mode resolution (quirks vs. strict) have now been fixed. You can document.write a DOCTYPE for example in a new document and have the correct mode be selected.

As with HTML, there is just enough information to be useful. Like HTML, it can be extended when necessary, but most people do it judiciously.

Probably the best-known strictness disaster is HTML. […]

Some people argue that HTML is commonly used because it’s not strict. That the non-strictness of its design makes it popular. That if web browsers had always just thrown an error instead of accepting invalid HTML, somehow people would not have used HTML. That is a patently ridiculous argument.

But sometimes, maintaining backwards compatibility for any area of your application can lead to a point of diminishing returns. This applies to everything about a program, not just its API.

The biggest obstacle for tasks above in conventional html/css is that box model. It does not support vertical alignment/flex. At all. You cannot say: "I want this table span the whole height of the view/container minus possible margins and borders". Thus we were forced to introduce "flex length units" to be able to support such typical UI tasks.

person A: P.S. The reason I did not understand the original message is that I do see wbr mentioned in the current draft of the html5, and I don't see where it declares that it is an error.

person B: It's not a parse error, but there's no way to include it in an HTML document without violating the content models.