Apple today released Safari 4.0.3 which is recommended for all Safari users and includes improvements to stability, compatibility and security including:
• Stability improvements for webpages that use the HTML 5 video tag
• Stability improvements for 3rd-party plug-ins
• Stability improvements for Top Sites
• Fixes an issue that prevented some users from logging into iWork.com
• Fixes an issue that could cause web content to be displayed in greyscale instead of color
Safari 4.0.3 is available via Software Update and also as a standalone installer.
More info and download links (40MB (Leopard), 26MB (Tiger), 27MB (Windows)) here.
For detailed information on the security content of this update, click here.
that still does not justify having to restart the system. a restart is a system-wide event… updating an application(s) is not… unless your talking about Internet Explorer and Windows… catch my drift?
Installing QuickTime requires a restart. That is because a lot of applications use QuickTime. Just like with WebKit. A lot of apps use its components. If you noticed, installing iTunes does NOT require a restart. Because installing iTunes is self-contained to just iTunes. Catch my drift?
It runs on my 800MHz eMac with Leopard.
BUG in Intel Safari 4.0.3 INSTALLER:
If you install Safari v4.0.3 and you find it locks up while loading a page, permanent sit-and-spin mode with the twirling lollipop of doom, RESTART your Mac AGAIN. Problem gone.
This is the second time within a week Apple have distributed an update with a faulty script. Shame on Apple. (And kids, I am no troll. When Apple f’s up, I say so. This is not flame bait. Settle down).
The other faulty script: For the original Combo update version of 10.5.8. It damaged the permissions database. Read all about it at MacFixIt. (The normal Software Update updater script was apparently not affected).
Anonymous ‘Jesus’ sez: “It does require a restart..! WTH Apple..! why do I have to restart my damn computer just to update the freaking browser?”
Why: The update requires and installs a newer, more secure version of Webkit, which is a fundamental piece of Mac OS X. Webkit is used by many other applications on the Mac, not just Safari. In order for any application, including Safari, to use the new version of Webkit, the OS must be restarted. PITA reminiscent of Windows restart hell, but in this case it actually makes logical sense.
Anonymous 5andman sez: “SUCKS!!!! Updated and now I get page freezes!”
See my first comment above about restarting your Mac AGAIN after installation. It’s a bug in the Intel installer script…
@ Jesus you ignorant slut;
What part of “Webkit is also used by Mail, iChat, and” other Apps can’t your feeble brain equate to being a system wide event?
Numbskull?
Webkit is NOT Safari, it’s a core technology used across the system and therefore IS a system wide event.
MW “saying” as in I’m just saying you’re a poor excuse for a troll
@MainMan
Listen up, good buddy. Take the contents out of /Library/InputManagers .. Safari should then work.. and, if it’s anything like my problem, you can then put the contents back in the InputManagers folder and it will *still* work (why? I do not know ..)
I might add that got really tired of Firefox by the time I got Safari working again. Just a matter of taste I guess… too many knobs and bells and whistles.
mooo, yes…. I’m a slut…. but that has nothing to do with my point…. every update to safari has required a restart in recent memory.
one of the major problems with Windows in the past was having to reboot after every update.
Having to restart after every Safari update reminds me of windows.
Not too long ago…. you pretty much never had to restart your Mac for anything but an OS update.
I understand why this needed a reboot… but it’s the idea of having to reboot every time Safari is updated that I am complaining about.
Microsoft has felt a lot of pain because of the way the integrated IE into the OS… I hope Apple does not go down the same road.
Already? Did Palm get a workaround that fast?
@ Jesus
> every update to safari has required a restart in recent memory.
And Safari every update in the future will as well, for reasons already explained and apparently not understood.
I did not realize there was an absolute rule that said, “If it’s an application update, don’t require a restart.” So you actually think it would be better and less confusing if the Safari software update process brought up a dialog that said, “Please quit the following applications: Safari, Mail, iChat, AddressBook…” and then monitored the system to make sure those applications (1) were closed and (2) were not reopened during the installation. And if the user forgot which apps they could not run and tried to run iChat, bring up a dialog that said, “iChat cannot be used at this time.”
Ten times as many clueless Mac users would be complaining about having to quit Mail to install Safari, and you would no doubt be one of them.
As usual, Apple made the smart choice and decided it was simpler and less confusing to tell the user a restart was required and lock the user out during the installation process, then restart the system. Obviously the right answer.
I believe it’s you that is missing the point.
I understand WHY the update requires a restart.. it’s not for the reason you stated above, btw (because it would be confusing for the user…). But lets run with that idea anyway. You honestly think its better to have an unnecessary restart instead of the update process simply interrupting the applications it is updating?
I should have to stop my work so my chat client and web browser can be updated???
Not an efficient way to do things.. and Apple stayed away from this philosophy for years.. which made the Apple experience that much better.
As I have said before.. integrating the web browser with the OS is a horrible idea… Doing so has been a major contributing factor to Microsoft’s security woes.. and will likely be a problem for Apple too (think “drive by” web exploits).
So lets clear this up.. just in case you still don’t understand.
We agree that Apple has made it necessary for a restart after a browser update.
You think this is a good idea… your reason given… so customers aren’t confused during the process?
I think it’s a bad idea.. for security and usability concerns.
@ Jesus
> As I have said before.. integrating the web browser with the OS is a horrible idea…
Please tell us how Safari is “integrated” into the OS. You make a statement as if it is true, yet do not present any facts. Just because a restart is needed to install Safari does NOT mean Safari is part of the OS.
@Jesus,
I’m pissed because I have to reboot my Mac when I install RAM. WTH? I have to shut down, plug in new stick, and push the power button! Is this ‘thinking differently?’ NO!
Yes Arnold… installing RAM and updating your browser are in the same league… what was i thinking. Thanks for clearing that up for me.
Ken, see moo’s post above regarding Webkit.
And if moo is wrong… ? and this is really only an update to the browser and it’s components…. having to reboot is even more ridiculous.
moo is just another poster. I don’t count him/her as an authority any more than I count you as one. I’m asking YOU to point to actual facts that indicate Safari is integrated (as you say) into the OS. You said it like you knew it was true, with no doubts about it.
I’ve already given my argument why it makes sense to require a restart. I don’t think my reasoning is “ridiculous,” because Apple is all about keeping it simple from the user’s perspective. Telling the user that a restart is needed is a more “useable” solution that telling the user to please quit these X applications. Locking the user account out during the installation process is also more “secure,” which (now that I think about it) may be a more important reason for requiring a restart.
Be aware of your frustration.
Doh!! Safari, not iTunes, Dummy.
What I get for posting before the coffee is made.
You have to do a reboot in OS X after any update that has Kernel level access.
WebKit is a .kext (Kernel Extension).. and as you pointed out.. many other apple applications need webkit to run.
Kernel and firmware updates should be the only things requiring system’s reboot…. everything else, including iTunes, iPhoto, , Safari….and Webkit, can be done with a simple service restart… but for some reason.. Apple tucked webkit deeply into the OS.
There is a big difference between having the OS tell you that it needs to quit your open webkit-based … and having to drop everything for a reboot… The only user interaction in the first scenario is to press a button.. the second scenario requires you to drop everything for a reboot.
There are a couple of Memory Leaks in the stuff that runs on my computer. While I suspect World of Warcraft is the main villain, I KNOW it is the one that does the most complaining – and failing. So … I wait until the situation gets annoying (WoW becomes erratic) then update and re-boot. Sometimes I just have to reboot without the update. Almost like running Windows, but much less frequent. I’m hoping SL (and more RAM) will either fix the problem or make the delay between reboots VERY long … yearly?
Wake me when this POS comes with an UNINSTALLER.
Anonymous ‘Jesus’ is very disappointing. He sez:
“WebKit is a .kext (Kernel Extension).. and as you pointed out.. many other apple applications need webkit to run.”
A) No one said it is a .kext. It is integrated into Mac OS X in two pieces that were replaced by the Safari 4.0.3 update:
(1) /System/Library/PrivateFrameworks/WebKitDashboardSupport.framework/Frameworks/Webkit.framework/Versions/A/Webkit
2) /System/Library/Frameworks/WebKit.framework
These are system level pieces of Mac OS X. You CAN’T just quit an application and restart it to have the application use the new frameworks. You have to RESTART THE OS. Got it? No? Then please STFU and do your homework before you post again. We are not here to do your homework for you.
are you that dense! That’s entirely my point! The browser and it’s components are so deeply embedded into the os that every update requires a reboot! You think it’s ok for your browser to be that deep into the system? Did you like Windows 95? Why is this so hard to understand?
You have no point.
Safari isn’t embedded into OS X at all, and WebKit isn’t a component belonging to it. “Deep into the system”? It’s about as deep into the system as Text Edit.
Maybe you should try using a Mac sometime.