Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Safari 2.0.1
- Thread starter clayj
- Start date
- Sort by reaction score
Your computer may not crash, but you don't get to play with the new toys either. Its a trade off. I'd rather have the added productivity that Spotlight, Dashboard, Automator, Expose, new versions of iLife bring than be able to brag about my computer never crashing. I like a stable comptuer as much as the next guy, but restarting once a month or so is not that big a deal.numediaman said:
ipacmm said:
Edmonds did not work correctly. Other sites had same problems. Screen would require a refresh to show.
On the sites I design, there were some major problems that 1.3 and 2.0 broke. If you don't create sites it won't make much sense. But as a background image for each section of my sites, I call on an image, menuimage.jpg. Every page calls on that image, however the image changes when you're in different sections, because you're in a different directory, and I have a different file there. It's a basic template kinda way of making pages.
Well, for some reason it quit working in 1.3. Whatever background image it first loaded would always be loaded if the file name was the same. Directory path be damned. IE and Firefox were fine. It wasn't a huge ordeal since probably only 1% of computer users out there are using Safari if that. But I do, and my main client does, so it was annoying.
So it seems like some errors were due to refreshing in some way, like my files, and whole pages like at edmonds.
And these problems have existed for at minimum 6 months. Very weak.
The image of doom will not crash anymore. Some people say it is still crashing their browser, but I'm willing to bet they haven't even emptied their cache!
It's a broken image. It shouldn't have crashed Safari, but it was being downloaded incorrectly. If it's still in your cache, and it was interpreted or downloaded incorrectly, then it's still going to crash the system. The fix must be some sort of download interpretation.
It's a broken image. It shouldn't have crashed Safari, but it was being downloaded incorrectly. If it's still in your cache, and it was interpreted or downloaded incorrectly, then it's still going to crash the system. The fix must be some sort of download interpretation.
bretm said:
Yep, you're right. It doesn't crash anymore. It used to before for me but now it's all good. Nice.
It hasn't made Safari compatible with Tinymce... http://tinymce.moxiecode.com/
What does this update do??
What does this update do??
Rantipole said:Could someone explain to me why it is NOT lame that OS10.3 users will not get a Safari 2?
10.3 users get the old Safari, the one without the flashy new component that makes it crash on the IoD
Still wondering when they will fully support Ajax. Forums such as VB, and Invision Power Board use the Ajax style interface and it makes posting for members alot easier. Running a Mac-Based forum myself, it is rather fustrating that every browser, other then the one bundled with OSX supports such extensions. Safari is a great browser, but they need to offer more flexability and the ability to alter and add mods such as FireFox offers mac and windows users alike.
I will continue to use safari.
Regards,
.Joel
I will continue to use safari.
Regards,
.Joel
Rantipole said:Could someone explain to me why it is NOT lame that OS10.3 users will not get a Safari 2?
Because presumably there is some underlying code in Safari 2 that is Tiger specific. And as others have said, some of Safari 2's features (Private Browsing and RSS feeds) are incentives for people to upgrade to Tiger.
The actual Webkit rendering code (the most important part of any browser) is still updated for Panther since 1.3 runs more or less in parallel to 2.0. The speed and compatibility gain that 1.3 gave over 1.2 was a big one - and Panther users are benefiting from it. The jump from Panther 1.3 to Tiger 2.0 was nowhere near as large as that one and was probably more to do with the general system performance increase than anything else.
ok, so im still waiting for it to appear in software update...
Anyone know why sometimes it takes ages for UK updates to come through?
I know i can download it seperately, but preffer to wait and do it through software update...
Anyone know why sometimes it takes ages for UK updates to come through?
I know i can download it seperately, but preffer to wait and do it through software update...
As far as I'm aware the updates all use the same severs,certainly the Safari update was available here in London as soon as this thread started in fact I got the iPhoto update several hours before it was mentioned here(5.01)deadfrog said:
I take back this post of mine. I just noticed when I am surfing MSN.com's News sites, Safari 2.0.1 showed horizontal scroll bar in the middle of the web site even though it should not be there. This is very strange. I then scroll up and down and this horizontal scroll bar then disappears. I guess this is one of the bugs which came with 2.0.1 update. Anyone having the same type of gliches?YS2003 said:
rendezvouscp said:
Sounds like he's a web devloper.
He noticed the first feature, specifically, because he was wanting to use it.As for the secound... Do you have any idea how annoying it is to change the image file, to fix some bug, and then have to go through all kinds of contortions to see if the fix worked because you can't get the browser to reload it?
Yes, in general it is a good idea to pull from cache. However, when I hit reload, it is very helpful to have the browser actually reload everything.
What exactly does Apple have to be sorry for?BWhaler said:
Granted I am a recent switcher, I am very content with Tiger and feel the money I spent on it was invested quite well.. Windows has never been able to become such an important work companion in 6 years as Tiger has become in 3 months...
deadfrog said:
Nope it was available to me, in the UK, as soon as I saw the thread here last night. Perhaps some odd cacheing issue with your ISP?
ohcrap said:
Hang around a little longer, or read through some old posts, and you'll discover that BWhaler's Tiger system appears to have every bug known, or unknown, to Apple in it without any apparent reasonable explanation as to why he's been so cursed.
You'll also discover that it particularly vexes him when more recent members tell him that their system is working just fine...
I've noticed some improvements:
1. I have a few auto-click bookmark folder with my favorites, between 10 and 14 sites that will open simultaneously upon a single click to the Bookmarks Bar. Before, they would (a) take a long time to load, and (b) as long as any one of them was loading, any page viewed would get the spinning beachball until the last page finished loading. After the update, the pages now load noticably faster, and once a certain page is finished, it is possible to scroll up and down and click on a link without the spinning beachball, even though one or more other pages in tabs are loading. In such a case, performance is slower, but the beachball no longer stops you dead.
2. In a similar situation as (1) above, when I had many tabs open, some of them would auto-update every x number of minutes, like Google News. When that happened, even if I was using a different window, I would again be beachballed. Now that interference is substantially reduced, though it does still happen some.
3. On some sites, especially ones like the New York Times, any attempt to select text, especially multiple-clicks on text, would result in wait times of up to 5 seconds per click--for example, if I double-clicked a word, I would have to wait for about ten seconds before the screen unfroze. No spinning beachball, but I simply couldn't do anything--scroll, switch tabs, etc. With the new version, that wait time on the same sites has been reduced to less than a second per click. Again, it still happens, but much faster.
***
A bug that still exists, aside from the ones listed above, is the first-window-popup-after-unhide bug. If you open more than one window in Safari, and are looking at a window other than the first when you hide the app, then unhide it, the first window pops up--even though any action you attempt will affect the window you were looking at when you hid Safari, despite that window being hidden behind the first window.
***
So, as I see it, there are some fixes, but some annoying bugs still persist. I was almost ready to switch back to Mozilla/Firefox when this update came in. I'll probably stay with Safari now, but not for certain--I'll have to see how it performs in the long run, if the fixes degrade over time, or if the 'fixes' I noted are not fixes but rather simply performace bumps due to the freshness of the version. I'm still annoyed by the bugs, but this version seems more bearable, while allowing me to enjoy the features Safari offers.
1. I have a few auto-click bookmark folder with my favorites, between 10 and 14 sites that will open simultaneously upon a single click to the Bookmarks Bar. Before, they would (a) take a long time to load, and (b) as long as any one of them was loading, any page viewed would get the spinning beachball until the last page finished loading. After the update, the pages now load noticably faster, and once a certain page is finished, it is possible to scroll up and down and click on a link without the spinning beachball, even though one or more other pages in tabs are loading. In such a case, performance is slower, but the beachball no longer stops you dead.
2. In a similar situation as (1) above, when I had many tabs open, some of them would auto-update every x number of minutes, like Google News. When that happened, even if I was using a different window, I would again be beachballed. Now that interference is substantially reduced, though it does still happen some.
3. On some sites, especially ones like the New York Times, any attempt to select text, especially multiple-clicks on text, would result in wait times of up to 5 seconds per click--for example, if I double-clicked a word, I would have to wait for about ten seconds before the screen unfroze. No spinning beachball, but I simply couldn't do anything--scroll, switch tabs, etc. With the new version, that wait time on the same sites has been reduced to less than a second per click. Again, it still happens, but much faster.
***
A bug that still exists, aside from the ones listed above, is the first-window-popup-after-unhide bug. If you open more than one window in Safari, and are looking at a window other than the first when you hide the app, then unhide it, the first window pops up--even though any action you attempt will affect the window you were looking at when you hid Safari, despite that window being hidden behind the first window.
***
So, as I see it, there are some fixes, but some annoying bugs still persist. I was almost ready to switch back to Mozilla/Firefox when this update came in. I'll probably stay with Safari now, but not for certain--I'll have to see how it performs in the long run, if the fixes degrade over time, or if the 'fixes' I noted are not fixes but rather simply performace bumps due to the freshness of the version. I'm still annoyed by the bugs, but this version seems more bearable, while allowing me to enjoy the features Safari offers.
I see.. you'll be in my prayers tonight, BWhaler.. lolApplespider said:Hang around a little longer, or read through some old posts, and you'll discover that BWhaler's Tiger system appears to have every bug known, or unknown, to Apple in it without any apparent reasonable explanation as to why he's been so cursed.
You'll also discover that it particularly vexes him when more recent members tell him that their system is working just fine...
rendezvouscp said:
Well sometimes you can use, let's say, a random background image which, when not reloaded properly, looses all of it utility...
jim. said:
That's exactly it. Now go look at some of the help requests through this board, and think about if you really want to explain to them how to do a 'sudo kill -HUP xxx' on a dependency chain.
Now as for the previous poster, I think its safe to assume that if you are building nightlies you are capable of doing a sighup.
Apple has done this right -- Software Update takes the conservative approach that even my grandmother could use.
For those of you who are so concerned about uptime (or are running production servers and need the uptime) Apple has provided you with an alternative -- just install the updates from the command line ('sudo softwareupdate -i blahblahblah') and sighup the necessary processes.
There best of both worlds, now people can stop complaining. Not that they will