Wow. This might be the stupidest behaviour from a browser that I’ve ever come across: mobile Safari behaves differently depending on the top level domain of the site! Madness!
Mind you… it’s kind of poetic justice for having a ridonkulous .mobi domain in the first place.
This is a very in-depth look at how to become a power user of the Web Inspector in Webkit browsers. I’m sitting down with a nice cup of tea to go through all of this.
Some very interesting results from testing background image downloads contained within media queries or overridden with media queries: it turns out that, in iOS at least, the browser is getting smarter and smarter.
That Scott is one smart cookie. He has come up with a workaround (using the accelerometer) for that annoying Mobile Safari orientation/zoom bug that I blogged about recently.
I still want Apple to fix this bug as soon as possible—the fact that such smart people are spending so much effort on ingenious hacks shows just how much of a pain-point this is.
Well, this is very intriguing: it turns out that the infamous orientation/scale bug in Mobile Safari isn’t present in in-app browsers (UIWebView). Most odd.
Finally. Hyphenation on the web.
Pretty much the only forms of Western literature that don’t use hyphenation are children’s books and websites. Until now.
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
The latest Webkit nightly includes the HTML5 parsing algorithm. Now it's a race between Firefox, Safari and Chrome to see which will be first (non-beta) browser to ship with the new parser.
A clear explanation of device-width from PPK.
PPK offers a rebuttal to Paul Graham's attack on Apple's App Store policies by placing the blame firmly at the feet of developers who refuse to embrace web technologies.
Experimenting with CSS3 and HTML5 features implemented in Webkit.
A blog of all things webkit, itself showcasing some of the CSS niceties in the rendering engine.
Neil explains how you can have your Safari cake and eat it.
The last piece is falling into place. IE8 has ARIA support, Mozilla has ARIA support ...and now WebKit is getting there. Excellent!
A comprehensive list of all the CSS properties supported in Safari including "a number of properties that are not supported for developer use."
Oh yes! A plugin for Safari that will detect, display and export hCard and hCalendar data. Caveat: it only works on Leopard so, because I haven't upgraded yet, I haven't had a chance to testdrive this yet myself.
I just learned from Kelly that Webkit is supporting local storage and database queries, as proposed in HTML5. Kinda like Google Gears. Potentially excited for the iPhone/iPod Touch.
Straight from the horse's mouth, advice for web developers on how the iPhone's browser renders pages. I'm very intrigued to find out how it handles liquid designs with no set min-width.
Got Safari? Try resizing this page.
Jon's mock-ups of how microformat detection and display might work in Safari are spot on. It would be so cool if this idea was picked up by browser developers.
Multiple background images (from CSS3) is implemented in Safari.... and has been for months!