as this seems to be similar:
http://www.adobe.com/devnet/html5/articles/css3-regions.html#articlecontentAdobe_numberedheader

Demo of CSS3 columns:(WebKit/Gecko):
http://weblogs.mozillazine.org/roc/

No need to reply, consider this a drive-by comment.

Thanks for contributing better typography smarts to WebKit.

Oh wait, Adobe’s the bag guy eh? I have my issues with Adobe (they really screwed me over recently by changing the rules about qualifying for educational software and then didn’t allow me to return the software unused) but their efforts to make the industries they serve more productive are appreciated by this graphics professional. (Let’s not even get into Acrobat Pro being out of sync with the creative suites.) I bring these things up to show I’m not Adobe sycophant.

Anyway, personal attacks against John Nack are uncalled for. He’s been a real gentleman for years as he maintains this blog and keeps us informed on what’s up with our favorite software tools for our jobs. I’d hate to see this devolve into such an ugly mess that he has to go back to moderating comments and even possibly deleting the worst of them.

As for getting justification sorted, I’m sure each browser will decide to interpret what ever justification algorithm/engine is used in its own individual way to make it look different in every browser anyway. Though I’m sure that will still be Adobe’s fault too, judging by the sort of comments you see here and elsewhere.
One can also be impressed by demos like this, even if it is obvious that the justification still needs work and the presentation is lacking polish.

We’ll also be looking at JS libraries to fill in the gaps when Browsers are slower to adopt.

Also, it views just fine on my iPhone and iPad, so YouTube is deliverying the content just fine. Your device or browser might suck, though.

[Perhaps. I naively copy & paste the markup that Google/YouTube give me. If their iFrame solution is great, why don't they give it to me, as Vimeo does? --J.]

Normally, I wouldn’t make a comment like this, but I’m appalled at your level of professionalism in the comments.

[Sorry to let you down. --J.]

It isn’t the responsibility of the browsing agent to rewrite the page to remove an explicit dependency on the Flash plugin. The fact that some browsing agents have been forced to do so is a large part of why many people consider non-Flash video playback standards to be so important.

sorry for the trouble I seem to cause with my blog post.

All I wanted to say, and said, was :

1. Good on Adobe to get on the webkit train and actively making progress to enhance it. And congratulations for this technical achievement.

2. The typography on this example doesn’t allow a basic and comfortable reading experience, but features a style effect for its own purpose. To the discomfort of the reader, who’s the one we should care about first and foremost.
Why doesn’t the effect work ? Not because this call out feature is a work in progress, but because you need a very good justification engine to perform it well. All I’m suggesting is : get the brains on the justification effort, and once and only then this foundation layer is fixed, bring the call out. I know it’s an effort representing thousands of man hours because you have to basically redo everything for each language, but if we want to get good call outs, we have to get through this. Otherwise it’s just lipstick on a pig. If we want to make the web a better place, we should resist to the urge to implement “press like” features for show off purposes, and aim the efforts at solving basic legibility problems.

3. A little more care could have gone into the making of the demo of this I’m-not-that-dumb-thank-you work in progress project: get a better lighting condition and the right white balance, stabilize the phone on a table and the camera on whatever’s handy. Get a Canon 5D (shouldn’t be hard to find at Adobe) to shoot for an even better image quality. That’s it. Not much effort nor time could bump the quality of what represents hours of brilliant peoples work on the web. A little more care.
As for the Apple reference, come on. You couldn’t find anything else than the giraffe to demonstrate the performance of this feature? I’m not opposing Apple to you, you understood it this way. I could have added that the justification support in iBooks sucks just as much, and that it shouldn’t be an option to display html or epub text this way today. You’re both on the same boat to this regard.

Also, the tone of my post seems to have irritate some of you. Let me just say that I was pissed. But more by a way of doing things – going for the spectacular while omitting more essential but discreet issues – than by the people involved in this project, you or Paul and his team. A reader cared to write to me his disappointment regarding this and said I sounded like an 11 years old child. Well, 11 years ago I wouldn’t have been able to write like this in english because it’s not my mother tongue. So indeed, I’m an 11 y.o. boy, there you go. Finding the right words has become easier, but some progress and fine tuning has to be made regarding the tone.