Surfin’ Safari
February 13, 2006
We have good news and bad news about Safari support. The good news is, we made it work! The bad news is, it requires a 4K flush on every pubsub event, which will make your process HUUUUGGGGEE in short order and probably crash your browser. This is due to a bug in Safari, which has long been fixed in Konquerer. So let me ask you Safari users what you prefer:
A) Damn the 4K flush, full speed ahead!
B) Harass the Apple team until they fix the bug
C) Grumble Firefox grumble
Let us know!
February 13, 2006 at 10:23 am
I love any option that involves harassing Apple.
Who specifically can we send our “Are we there yet?”s to?
February 13, 2006 at 11:28 am
So, have you filed a bug against WebKit, and asked on the forums to see if somebody has even looked at your bug?
webkit.opendarwin.org
Why not (d) fix the bug yourself?
The more constructive the harassment, the better chance of success.
February 13, 2006 at 5:52 pm
Ernie, we’re talking about Safari on OSX.
Darwin doesn’t have Aqua and Safari, right?
February 14, 2006 at 11:12 pm
Hey Adam, in cases you missed the news last year, Apple has open-sourced webkit, which is the core of Safari. Webkit now has nightly builds on the opendarwin project’s wiki… see http://webkit.opendarwin.org/ If you’re engaged in debugging Safari, be sure to check out the Element Inspector the project recently made available for Webkit… see http://webkit.opendarwin.org/blog/?p=41 It’s pretty amazing.
And by all means do your testing on both Safari and the Webkit nightly builds. Webkit has fixed a lot of bugs already that haven’t made it into Apple’s official release.
February 15, 2006 at 3:35 pm
Got it. So in a future Apple official release, Safari will no longer need a flush. Cool.
June 18, 2006 at 4:38 pm
Here’s some more information, but we’re still waiting on Safari support.
Chris Shiflett has a good explanation of the problem we’re seeing.
Basically our issue with Safari is that instead of the chunk size and then the chunk triggering progressive rendering, Safari seems to wait for a 1K flush. This behavior has long been fixed in Konqueror, btw. (1K flush is not required on Firefox; in Internet Explorer, we can send a single br tag to get progressive rendering to happen.)
June 26, 2006 at 3:25 pm
Damn the 4k flush! Full speed ahead.
June 27, 2006 at 9:43 pm
Dustin, I like your attitude.
December 10, 2006 at 10:03 pm
How about you have the magic front page detect whether or not I’m running the crappy ancient stock Safari versus a shiny new build using a later WebKit? I’m tired of being shut out for a reason that doesn’t apply to me anymore. Sigh.
December 14, 2006 at 11:28 pm
Thank you for letting us know, Masque!
We’re currently doing another round of testing and will work on it as fast as we can.
December 17, 2006 at 1:54 pm
Any chance you could stop blocking Camino? It uses the same Gecko render engine as Firefox (but is a much zippier browser and I prefer it), so it shouldn’t have any trouble with your site. Please add it to the supported browsers list. Thanks.
December 18, 2006 at 3:53 am
Please stop blocking Camino,
It does use the same engine as firefox, and is the only viable OSX gecko based browser.