optikz writes "Apple has just released Safari 1.0 and it is availlable via Software Update. This release is now out of the 'beta' stage. It is version 1.0 (v85)." Not much appears to have changed since the last beta. I just need to decide if it should replace Camino for me.
Seems faster
by
Llywelyn
·
· Score: 4, Informative
While I don't have any benchmarks, it seems faster and more responsive overall. This wouldn't surprise me, since they've probably removed a good deal of the debug code.
It still has a bad habit of trying to deeplink itself into CNN every time I go there and a few rendering fragments when a text box crosses the address/status bar, but other than that it seems very solid as a release.
There are no real improvements in the prefs panel since last time either, which is unfortunate.
Re:This is not my beautiful (first?) post!
by
gerbache
·
· Score: 3, Informative
Yeah, the trouble with so many mac stories coming out so quickly during the keynote is that the discussions between all of them ended up sounding much the same. Oh well, I'd rather that than have the keynote turn out to be a flop.
As for Safari, I've been impressed with it as a whole. I can't say it's a huge difference for me over Camino, but it's really nice to have a choice of several native Aqua web browsers to choose from. I actually kinda like the metal look to the new Apple programs, although it would be nice if they'd all settle on one appearance...
The default font has also changed to Times. Pages rendered look much more like IE now.
Re:CSS Support?
by
Michael.Forman
·
· Score: 2, Informative
The CSS support in Safari is excellent!
I have advanced CSS-generated menus and simulated CSS transparencies on my home page. This complex CSS didn't render in the first Safari releases but quickly improved as new releases came out. Currently it renders my home page as well as Mozilla does. As a matter of fact all the development of my website has moved from my Linux box to my Powerbook. (I used to use Linux, vi, and Mozilla. Now I use MacOS, vi, and Safari.)
:wq
Michael.
-- Linux : Mac:: VW : Mercedes
Re:Still a little buggy
by
babbage
·
· Score: 4, Informative
Don't tell us -- file a bug! If you had it active before, the "bug" icon may have gone away with the 1.0 upgrade, but it can be restored, and "Repot bugs to Apple..." is still the second item under the Safari menu.
The Safari group has been responsive to bug fixes so far, and hopefully will continue to be now that the first milestone release is out of the way.
I still wish that yo ucould tab to all active page elements, not just text fields. Must go submit that one myself...
Re:Some stuff still needs fixin'
by
Anonymous Coward
·
· Score: 1, Informative
I had problem like #2 for a while but it was fixed a couple builds ago. Are you using the newest versions in these tests?
The problem was that Safari didn't issue a CONNECT command to the proxy, to tunnel to the secure host. Most proxies doesn't speak SSL but Safari was trying to talk SSL directly to the proxy, when it should've first asked the proxy to tunnel to the remote SSL host.
The iTunes music store had the same annoying problem, which was fixed in 4.0.1.
You can debug it with tcpdump or something. Compare the packets from another web browser and you'll see it.
Re:Some stuff still needs fixin'
by
bedouin
·
· Score: 4, Informative
http sites load okay, but https sites do not work at all.
Just curious, have you tried it recently? There was a bug in early builds of Safari where secure proxies simply didn't work; it's since been fixed.
Re:Cross-platform web design issue
by
thumperward
·
· Score: 4, Informative
Webcore renders in a similar way to Gecko. If you absolutely must know how it renders in Safari though, get a Knoppix CD and check with Konqueror.
- Chris
Re:Gripes about Safari 1.0
by
thumperward
·
· Score: 2, Informative
Minimum font size was removed because some sites use small fonts as spacers and having a minimum set for that broke said sites badly. Apparently. Anyway, you've got a font zoom haven't you?
- Chris
Beware if you use PithHelmet
by
Doodads
·
· Score: 2, Informative
A warning to those of you using PithHelmet to block images. Remove it! It stopped the new version from launching and I couldn't even use my old version after I upgraded.
If you have PithHelmet installed go to : <harddrive>:Library:InputManagers:SIMBL and get rid of it. Or don't upgrade.
Too bad I don't have image blocking anymore.
Re:Beware if you use PithHelmet
by
Erik+K.+Veland
·
· Score: 2, Informative
PithHelmet is updated for Safari 1.0, you just need to replace ~/Library/InputManagers/SIMBL/Plugins/PithHelmet.b undle with this file. Bye bye ads!
-- "I tend to think of OS X as Linux with QA and Taste", James Gosling, creator of Java
Re:What was the default font before?
by
PurpleRabbit
·
· Score: 2, Informative
The last Safari beta (v74) used Lucida Grande 14 as default font.
I find it strange that a switch has been made to a serif font - Times - as default. The "frilly bits" added to the letters in a serif font were designed so that text could still be read even if printed onto cheap paper that let the ink spread. On screen, a sans-serif (no "frilly bits") font is far more readable and so makes much more sense. e.g. Lucida, Arial.
Who cares if pages render like they do through M$IE if it looks like crap? The good news is that it can be changed in preferences.
--
I'm on a whisky diet. I've lost three days already.
What IS the default font NOW?
by
PurpleRabbit
·
· Score: 2, Informative
Now I've updated Safari, the default font for me is Helvetica 14. (Sans-serif: makes sense, looks good.)
Not sure how you ended up with Times...
--
I'm on a whisky diet. I've lost three days already.
RAM Disk in OS X and how to move Safari's cache
by
SensitiveMale
·
· Score: 5, Informative
70% of this code isn't mine, but found I bits everywhere.
The first part is a AppleScript. It does a few things. First it creates the RAM disk. Then it renames the RAM disk. Then it automatically starts Safari. The reason why I have it start Safari is to ensure the RAM disk is up and running at login before Safari is launched.
Where you see the line "set diskSize to 40" sets the RAM disk's size. 40 is 40 Megs. Simply change that to whatever size you want.
Copy and paste the script into the script editor, Save it as "application" and be sure to uncheck the box "Never show startup screen".
tell application "Finder"
activate
set diskSize to 40
set diskSize to diskSize * 2048
do shell script "hdid -nomount ram://" & diskSize
set dskImg to the result
set prevTextDelims to AppleScript's text item delimiters
set AppleScript's text item delimiters to {"/"}
set myDevDisk to the last text item of dskImg
set myShellCmd to "/sbin/newfs_hfs/dev/r" & myDevDisk as text
do shell script myShellCmd
do shell script "hdiutil mount/dev/" & myDevDisk
set AppleScript's text item delimiters to prevTextDelims
end tell
delay (1)
tell application "Finder"
set name of item "untitled" to "RAM Disk"
end tell
tell application "Safari"
launch
end tell
Here is how you move Safari's cache to the RAM Disk.
Re:What was the default font before?
by
ProfKyne
·
· Score: 4, Informative
You guys are still all wrong about that. The serifs were used in print in an attempt to replicate the carved stone lettering that adorned buildings and stone-cut signs. And the reason why those serifs appeared (on stone-cut signs) was because the stone was often very brittle and would crumble at the corners of the letters. So the stonecutters adopted a style that would still look good while accounting for this inadvertent crumbling.
My dad told me this when I was a kid. He got a master's degree in print technology from RIT -- I believe him.
-- "First you gotta do the truffle shuffle."
Re:Cross-platform web design issue
by
Viqsi
·
· Score: 3, Informative
This is insufficient, because WebCore fixes a lot of bugs still present in the latest KHTML. I found this out (to my unceasing joy:D ) when a friend of mine with MacOS X started testing a few sites for me.
(For the record, the two that I've noticed so far are: 1) Safari knows how to draw a "dotted" border properly, and 2) Safari appears to support the max-width: property.)
--
-- viqsi - See "vixen" If we do not change our direction we are likely to end up where we are headed.
Re:Buttons are better
by
aftk2
·
· Score: 2, Informative
I wonder if Safari's displaying button as a block level element. If you put this into a CSS file...
button {display: inline; margin-right: 5px}
Maybe it would display all buttons on a single line, with some margin between them.
Aah, well...I can't test this anyway. The burden's of being poor...
-- concrete5: a cms made for marketing, but strong enough for geeks.
No Keychain, No Safari
by
Clock+Nova
·
· Score: 3, Informative
I can never switch from Camino to Safari until Safari is able to access the nearly 100 user and password entries that Camino has saved in my OSX Keychain. This is ridiculous.
-- There they were, sitting in the van with all those dials, and the cat was dead.
-V. Marchetti, CIA
possible fixes.... Re:On-line banking?
by
johnpaul191
·
· Score: 2, Informative
there are a few possible fixes to get it to work.
1) does your bank require pop-ups? seems simple, but i totally forgot one site i use an account to order from has a customer pop-up window. i assumed the site was bunk (mozilla blocking my pop-ups too) till safari told me the reason for the error.
2) you can tell Safari to identify itself as M$IE or whatever in the prefs. I know some sites work fine once you do this (like my university's student login thing)
3) there is a cache issue. you can try downloading Safari Enhancer . It lets you do fun things like access the debug menu and disable cache, and easily import Mozilla bookmarks. Safari is a fast browser, so with DSL i barely notice the cache being turned off and it seemed to be the only way for some sites to work properly (like some phpNuke sites i log in for).
Finally be sure you submit the bug to Apple again so they know 1.0 still fails. It's possible it's the bank's fault, but maybe not. Even if it is the bank, somebody should tell them. If AOL really dumps IE and Mac stop shipping with it, webmasters will hopefully return to following standards.
Another possible fix: Change your security setting to accept all cookies. I had mine set to reject third-party cookies (to prevent marketing spyware), and that was keeping me from accessing online bill-pay at my bank.
Slashdot Mirror
While I don't have any benchmarks, it seems faster and more responsive overall. This wouldn't surprise me, since they've probably removed a good deal of the debug code.
It still has a bad habit of trying to deeplink itself into CNN every time I go there and a few rendering fragments when a text box crosses the address/status bar, but other than that it seems very solid as a release.
There are no real improvements in the prefs panel since last time either, which is unfortunate.
Integrate Keynote and LaTeX
Yeah, the trouble with so many mac stories coming out so quickly during the keynote is that the discussions between all of them ended up sounding much the same. Oh well, I'd rather that than have the keynote turn out to be a flop.
As for Safari, I've been impressed with it as a whole. I can't say it's a huge difference for me over Camino, but it's really nice to have a choice of several native Aqua web browsers to choose from. I actually kinda like the metal look to the new Apple programs, although it would be nice if they'd all settle on one appearance...
The default font has also changed to Times. Pages rendered look much more like IE now.
The CSS support in Safari is excellent!
:wq
I have advanced CSS-generated menus and simulated CSS transparencies on my home page. This complex CSS didn't render in the first Safari releases but quickly improved as new releases came out. Currently it renders my home page as well as Mozilla does. As a matter of fact all the development of my website has moved from my Linux box to my Powerbook. (I used to use Linux, vi, and Mozilla. Now I use MacOS, vi, and Safari.)
Michael.
Linux : Mac
The Safari group has been responsive to bug fixes so far, and hopefully will continue to be now that the first milestone release is out of the way.
I still wish that yo ucould tab to all active page elements, not just text fields. Must go submit that one myself...
DO NOT LEAVE IT IS NOT REAL
I had problem like #2 for a while but it was fixed a couple builds ago. Are you using the newest versions in these tests?
The problem was that Safari didn't issue a CONNECT command to the proxy, to tunnel to the secure host. Most proxies doesn't speak SSL but Safari was trying to talk SSL directly to the proxy, when it should've first asked the proxy to tunnel to the remote SSL host.
The iTunes music store had the same annoying problem, which was fixed in 4.0.1.
You can debug it with tcpdump or something. Compare the packets from another web browser and you'll see it.
http sites load okay, but https sites do not work at all.
Just curious, have you tried it recently? There was a bug in early builds of Safari where secure proxies simply didn't work; it's since been fixed.
Webcore renders in a similar way to Gecko. If you absolutely must know how it renders in Safari though, get a Knoppix CD and check with Konqueror.
- Chris
Minimum font size was removed because some sites use small fonts as spacers and having a minimum set for that broke said sites badly. Apparently. Anyway, you've got a font zoom haven't you?
- Chris
A warning to those of you using PithHelmet to block images. Remove it! It stopped the new version from launching and I couldn't even use my old version after I upgraded.
If you have PithHelmet installed go to : <harddrive>:Library:InputManagers:SIMBL and get rid of it. Or don't upgrade.
Too bad I don't have image blocking anymore.
The last Safari beta (v74) used Lucida Grande 14 as default font.
I find it strange that a switch has been made to a serif font - Times - as default. The "frilly bits" added to the letters in a serif font were designed so that text could still be read even if printed onto cheap paper that let the ink spread. On screen, a sans-serif (no "frilly bits") font is far more readable and so makes much more sense. e.g. Lucida, Arial.
Who cares if pages render like they do through M$IE if it looks like crap? The good news is that it can be changed in preferences.
I'm on a whisky diet. I've lost three days already.
Now I've updated Safari, the default font for me is Helvetica 14. (Sans-serif: makes sense, looks good.)
Not sure how you ended up with Times...
I'm on a whisky diet. I've lost three days already.
70% of this code isn't mine, but found I bits everywhere.
/dev/r" & myDevDisk as text /dev/" & myDevDisk
The first part is a AppleScript. It does a few things. First it creates the RAM disk. Then it renames the RAM disk. Then it automatically starts Safari. The reason why I have it start Safari is to ensure the RAM disk is up and running at login before Safari is launched.
Where you see the line "set diskSize to 40" sets the RAM disk's size. 40 is 40 Megs. Simply change that to whatever size you want.
Copy and paste the script into the script editor, Save it as "application" and be sure to uncheck the box "Never show startup screen".
tell application "Finder"
activate
set diskSize to 40
set diskSize to diskSize * 2048
do shell script "hdid -nomount ram://" & diskSize
set dskImg to the result
set prevTextDelims to AppleScript's text item delimiters
set AppleScript's text item delimiters to {"/"}
set myDevDisk to the last text item of dskImg
set myShellCmd to "/sbin/newfs_hfs
do shell script myShellCmd
do shell script "hdiutil mount
set AppleScript's text item delimiters to prevTextDelims
end tell
delay (1)
tell application "Finder"
set name of item "untitled" to "RAM Disk"
end tell
tell application "Safari"
launch
end tell
Here is how you move Safari's cache to the RAM Disk.
Close Safari.
Open terminal.
Run this command -
ditto -rsrc ~/Library/Caches/Safari "/Volumes/RAM Disk/"
Then delete the folder "your home/library/caches/safari"
Run this command -
ln -s "/Volumes/RAM Disk" ~/Library/Caches/Safari
That will create the link between the RAM disk and your safari cache folder.
That's it. Works perfectly and much much faster.
You will have to run the applescript at login.
You only have to run the terminal commands once.
Another poster was kind enough to point out to me that you can enable the bug button from inside of the "View" menu.
Integrate Keynote and LaTeX
You guys are still all wrong about that. The serifs were used in print in an attempt to replicate the carved stone lettering that adorned buildings and stone-cut signs. And the reason why those serifs appeared (on stone-cut signs) was because the stone was often very brittle and would crumble at the corners of the letters. So the stonecutters adopted a style that would still look good while accounting for this inadvertent crumbling.
My dad told me this when I was a kid. He got a master's degree in print technology from RIT -- I believe him.
"First you gotta do the truffle shuffle."
This is insufficient, because WebCore fixes a lot of bugs still present in the latest KHTML. I found this out (to my unceasing joy :D ) when a friend of mine with MacOS X started testing a few sites for me.
(For the record, the two that I've noticed so far are:
1) Safari knows how to draw a "dotted" border properly, and
2) Safari appears to support the max-width: property.)
--
viqsi - See "vixen"
If we do not change our direction we are likely to end up where we are headed.
I wonder if Safari's displaying button as a block level element. If you put this into a CSS file...
button {display: inline; margin-right: 5px}
Maybe it would display all buttons on a single line, with some margin between them.
Aah, well...I can't test this anyway. The burden's of being poor...
concrete5: a cms made for marketing, but strong enough for geeks.
I can never switch from Camino to Safari until Safari is able to access the nearly 100 user and password entries that Camino has saved in my OSX Keychain. This is ridiculous.
There they were, sitting in the van with all those dials, and the cat was dead. -V. Marchetti, CIA
there are a few possible fixes to get it to work.
1) does your bank require pop-ups? seems simple, but i totally forgot one site i use an account to order from has a customer pop-up window. i assumed the site was bunk (mozilla blocking my pop-ups too) till safari told me the reason for the error.
2) you can tell Safari to identify itself as M$IE or whatever in the prefs. I know some sites work fine once you do this (like my university's student login thing)
3) there is a cache issue. you can try downloading Safari Enhancer . It lets you do fun things like access the debug menu and disable cache, and easily import Mozilla bookmarks. Safari is a fast browser, so with DSL i barely notice the cache being turned off and it seemed to be the only way for some sites to work properly (like some phpNuke sites i log in for).
Finally be sure you submit the bug to Apple again so they know 1.0 still fails. It's possible it's the bank's fault, but maybe not. Even if it is the bank, somebody should tell them. If AOL really dumps IE and Mac stop shipping with it, webmasters will hopefully return to following standards.