A good history lesson in rendering engines: KHTML, WebKit, and now, Blink.
A cautionary tale from Stuart. We, the makers of modern technology, are letting people down. Badly.
We’re in this to help users, remember: not just the ones who think as we do, but the ones who rely on us to build things for them because they don’t know what they’re doing. If your response is honestly “well, he should have spent more on a phone to get something better”, then I’m exceedingly disillusioned by you.
Brad is on a roll. He knocks it out of the park again, this time talking about the difference between supporting the huge range of mobile browsers out there compared to trying to optimise for them.
It’s Opera …but it’s folk.
An eye-opening insight into web usage on mobile devices in Asia from Paul Rouget.
In an attempt to “optimise” performance, T-Mobile and Orange are actually breaking jQuery.
Here’s a video of the mobile browser panel I moderated at Mobilism in Amsterdam today. It gets fairly technical for a while but it was mostly a lot of fun.
A rather vicious evaluation of browser support for the audio element and the audio API. It is divided up into:
- Browsers From Companies That Actually Care About HTML5 Audio
- Browsers From Companies That Hate the Web Enough to Not Support Ogg/Vorbis, but do Have an Audio Tag So They Can Say They Have an Audio Tag (Seriously, Fuck You)
- Browsers That Say They Support HTML5 Audio But Actually Don’t Support HTML5 Audio
Some musings from Norman Walsh. I have to say, I’m still not entirely sure why the HTML/XML Task Force exists. The “use cases” described here are vague and handwavey.
All the tests and all the results, all in one place.
A nifty idea to help you people save on postage by clubbing together to make a single Amazon purchase.
Here's a little piece of web history: the proposal that was presented and rejected at the 2004 W3C workshop that led to the formation of the WHATWG.
Matt Ridley's new book sounds like a corker.
Mozilla, Opera and Google are collaborating on an open format for audio and video for the web (a wrapper for Vorbis for audio and VP8 for video).
Microsoft, Mozilla and Opera have formally submitted the WOFF font format to the W3C.
Bert Bos's 2000 Treatise (published in 2003) is a must-read for anyone involved in developing any kind of format. "This essay tries to make explicit what the developers in the various W3C working groups mean when they invoke words like efficiency, maintainability, accessibility, extensibility, learnability, simplicity, longevity, and other long words ending in -y."
An excellent write-up by Bruce of a talk he gave at the Betavine birthday party. Down with .mobi! One Web FTW!
This presentation by Steven Pemberton increases in value over time.
Christopher Schmitt shows how to style XFN links using attribute selectors.
Opera have unveiled the Web Standards Curriculum. It's released under a CC attribution non-commercial share-alike license and it looks like a very valuable resource.
David has no sense of humour.
PPK points out a potentially dangerous aspect to Opera's actions, one that that the rest of us have missed: "Without consulting anybody, Opera is trying to give a political body the right to decide what does and what does not constitute a web standard."
Ben Buchanan on how most supposedly open Web 2.0 (sic) sites are really walled gardens lacking interoperability.
As in beer.
The DOM support looks great.