Submitted by Apple updates Safari to 2.01, the site says improved website support. You can download this update via Software Update. My Take: I downloaded the update. Due to server load haven’t been able to test the image of doom, will be a shame if that problem is still there.
does this version pass the acid2 test?
No, it doesn’t pass acid2.
You need to download the latest webkit for this.
http://webkit.opendarwin.org/
Apple might be upgrading to the new webkit with 10.4.3
Hrrm… I followed the directions and I keep getting a password error.
Why is this somehow important? Do you happen to know any site that uses any of those Acid2 “options” in real life?
> Why is this somehow important? Do you happen to
> know any site that uses any of those Acid2
> “options” in real life?
No, but that’s not surprising as I haven’t done any research on that.
Having standard-conforming error handling means for example that no compliant browser the web developer happens to test his code in will silently ignore a certain error while other implementors of the standard will not. -> Errors will be handled the same or, even better, get fixed.
And now please don’t tell me that the web is not full of broken pages that just happened to work in some browser.
No one uses any acid2-like code because browsers won’t accept it (even though it is standard). That’s why it is important to fix. Once those features are properly implemented, more sites can use those features if needed.
image of doom still dooms safari, news @ 11
Is there more information about what exactly they did anyplace? Like, the specific improvements would be nice to know…
“Safari could not open the page “http://www.drunkenblog.com/drunkenblog-archives/i/kthmlwebkit_crash… because the server stopped responding.”
Oh the irony, so many people are trying to crash their browser that they melt down the server 🙂
So I finally got through and the ‘image of doom’ didn’t crash Safari while it did before the update. I’m using OSX 10.4.2.
Ahem, correction : loading the image WON’T crash Safari, reloading the image WILL. At least here, ymmv.
To bad !
I’m with OS X 10.3.9 and Safari just got updated to 1.3.1.
It seems that OSN is overusing “My Take” –
My take signifies your OPINION, your view, what you think. Since you have not installed it yet, and have not tried it yet – you officially dont have a reason to say “my take”
Since this is not even your site (or mine for that matter) you officially don’t have the right to bitch about anything.
Why must I restart my Mac after installing the update :/
Very annoying
What really got updated is the webkit component, not Safari. The webkit is used all through OS X, much like IE in windows (Dashboard, help, etc.).
It is frustrating, however, that an update to the “browser” necessitates a system restart.
Thank you very much for the clarification in terms I understand. I’m a windows power user, but just recently bought a MacMini to run as a home server, it’s a delightful machine and ultra silent!
Why must I restart my Mac after installing the update :/
Very annoying
Agreed, it seems kind of silly. Even worse is the fact that there’s no “restart later” button on the reboot dialog. I’m just gonna have to hide it until I feel like rebooting…
“Why must I restart my Mac after installing the update :/
Very annoying
Agreed, it seems kind of silly. Even worse is the fact that there’s no “restart later” button on the reboot dialog. I’m just gonna have to hide it until I feel like rebooting…”
Apple is learning with Windoze…
Restarting a computer because the browser is updated? How Microsoft like!
I will have to second mini-me:
I was always curious to read about what somebody is downloading *just now*, with some added conjecture. How big is it 500 MB? 2 GB? Why didn’t you wait for like 8 seconds and then tell us that you actually *did* download it and how it really was. You must be still downloading, I guess…
Premature speculation seems to be the norm in news these days. That’s basically all television news channels seem to do.
Not that I’m saying it’s good or bad. It’s just an interesting aspect of reporting. To be honest I don’t see why he didn’t just post a comment like everyone else does, but it’s not a big deal.
How about not causing CPU spikes and hogging all my memory!
acid 2 isn’t even legit web code. why should anyone care if it gets rendered properly??
> acid 2 isn’t even legit web code.
That’s the point. It tests, among other things, error handling and is picky about certain features, e.g. HTML comments.
> why should anyone care if it gets rendered properly??
Because the W3C standards say so. It’s crafted so that you get a smiley if the browser is *compliant*. The test is *not* about displaying garbage code alright by *ignoring* the standards. Don’t mix up these two things.
That’s the point. It tests, among other things, error handling and is picky about certain features, e.g. HTML comments.
Because there are just so many ways you can confuse a HTML comment with code. Like is this: “<– — ->” a comment or code? Instead of focusing on real problems the “test” tests some stupid error handling no one cares about. You should read Hyatt’s blog about his progress when trying to pass Acid2.
I usually just Force Quit the installer.
Safari crashed before the update, and still crashes after the update.
Tibook 667 10.4.2
Doesn’t crash for me after the update.
if you run software update from the terminal you don’t have to reboot after updates. just run man softwareupdate
An anemic update at best. Fixes some bugs which shouldn’t have been there in the first place. And the massive memory leak issues have not been repaired.
I really hope 10.4.3 is the Tiger release with the quality we expect from Apple.
I have no idea why Apple released Tiger before it was due. After the Tiger experience, I will definitely be more cautious when Leopard is released and wait 6-8 months before buying it. I, like many Mac folks, have simply been burned too badly with the Tiger experience.
what are you doing that’s causing these memory leaks or exposing such massive bugs?
i have not had any poblems with tiger so i’m curious
Well, they still didn’t fix the memory leak, and as with every update the come out with, safari leaks even faster. Woohoo, browser using into the Gigs of ram in a few hours with just a few tabs.
Fix this before you fix website compatibility apple!
This is not a major update of Safari. This is an update of Safari 2.0/1.3 (or the webkit behind both of those specifically) to fix the regression of that update. That is, Safari 2.0/1.3 broke a couple small web features from Safari 1.2, and they are small, self-contained features that web developers depend on (such as being able to add a row to a table at any index with Javascript – this got broken in 2.0/1.3). So, here Apple is fixing the regressions, and waiting for 10.4.3 to do the next big update to Safari. Most likely, this regression-fix update is the last one Panther is going to receive (apart from security updates). So, nothing to see here – move along folks.
apple sucks, osx sucks, safari sucks.