Oh Well
Didn't fix either of the two problems I continue to have. Gettin' reaaaaaaaal old, Apple.
Didn't fix either of the two problems I continue to have. Gettin' reaaaaaaaal old, Apple.
cemorris said:Yeah I can finnally log into fredmiranda.com forums!!! Hooray!!
And this right here ladies and gentleman is why I believe Apple should institute some type of "system restore" feature similar to Windows XP. Please don't give me that crap about why it's not needed b/c OS X is so much more stable. It certainly is but there is always exceptions, and to require someone to do a complete reinstall, to circumvent some unknown issue is kind of ridiculous. Just imho...Object-X said:My system is completely hosed. Finder is crashing my system, the icons are all missing, .dmg packages are not working. This really sucks.
Could someone explain to me why it is NOT lame that OS10.3 users will not get a Safari 2?Makosuke said:Safari 1.3.1 is also showing up for 10.3 users:
Rantipole said:Could someone explain to me why it is NOT lame that OS10.3 users will not get a Safari 2?
You mean "Tiger and not Panther" of course.rdowns said:Because Safari 2 requires components that are part of Panther and not Jaguar.
Rantipole said:Could someone explain to me why it is NOT lame that OS10.3 users will not get a Safari 2?
Rantipole said:Could someone explain to me why it is NOT lame that OS10.3 users will not get a Safari 2?
That topic's been covered already in this thread. It probably made changes to WebKit.bubbalwz said:Come on Apple... Does windows even require a reboot for a web browser update? I only reboot for kernel updates on my linux box.
Or Dashoboard and Spotlight for that matter...Rantipole said:Could someone explain to me why it is NOT lame that OS10.3 users will not get a Safari 2?
Heb1228 said:That topic's been covered already in this thread. It probably made changes to WebKit.
aegisdesign said:Not actually a reason to have to reboot as I download a new nightly safari WebKit build every couple of days. At the moment the nightly supports some of the CSS3 border-radius draft. Very nice too.
I suspect it's just easier for Apple to control the state of the machine if they can restart all the other apps they don't know about that may be using WebKit.
Incidentally, this one fixes two bugs so far that I've come across.
1) background images that are in the cache don't get reloaded on every page. That was annoying me a lot.
2) unordered lists with graphics for bullets get the offset right now.
I do believe that the nightly Webkit builds that you are downloading are statically linked within the nightly safari build. Naturally, since no other apps that are running would depend on these libs, no reboot should be required.aegisdesign said:Not actually a reason to have to reboot as I download a new nightly safari WebKit build every couple of days.
Figures...numediaman said:In fact, the only time I've ever had an issue with the OS was when I accidently opened up Internet Explorer
Kind of. Saft will not load after the update, but if you want you can edit the info.plist file in the saft bundle to change the safari version key to 412.5. If you do that, then Saft works just fine.yg17 said:Does this update break Saft?