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.
This is not my beautiful (first?) post!
by
AvantLegion
·
· Score: 2, Troll
This was talked about in comments many hours ago in other Apple-related stories.
Oh well. Anyway, I'm getting an iBook soon and look forward to playing around with Safari.
Re:This is not my beautiful (first?) post!
by
dalassa
·
· Score: 2
But it is my beautiful webrowser. Water flowing underground even.
Just updated and I'v already noticed differences in the way sites load. Some sites that didn't load without being rendered unreadable are rendering nicely now.
-- Feminism is the radical notion that women are people.
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...
Even 1.0 STILL won't work correctly with my On-line banking!
AARRGGHH!!
-- I only came here to do two things; kick some ass, and drink some beer...looks like we're almost out of beer.
Re:On-line banking?
by
djupedal
·
· Score: 4, Funny
I can get into your account with it, no issue:) - Man, you have got to do a better job saving...
Re:On-line banking?
by
PurpleRabbit
·
· Score: 3, Interesting
Safari v85 also still doesn't work with ThinkGeek accounts (bug submitted through v74, just in case). Now, at least, ThinkGeek acknowledge it, which wasn't the case when I first happened upon the problem for myself.
They say:
"Attention Safari Users: Due to a problem with Safari reading cookies on our site, Safari users are unable to log into the site. The problem should be resolved soon, but in the meantime, please use a different browser such as Mozilla, Netscape, or Internet Explorer. Sorry for the inconvenience!"
Is it ironic only to me that OSDN are pointing people to using (among other things) M$IE?
--
I'm on a whisky diet. I've lost three days already.
Nearly perfect timing, too. IE's gone, Safari's here... out with the old, in with the new.
Re:Good stuff
by
cloudless.net
·
· Score: 5, Interesting
I bet Apple already knew IE would be gone on Mac OS, before starting to develop Safari.
Re:Good stuff
by
Farley+Mullet
·
· Score: 2, Insightful
I bet Apple already knew IE would be gone on Mac OS, before starting to develop Safari.
Yeah, but I bet developing the iTunes Music store, with its need for embedded HTML rendering, had more to do with do with developing Safari and the WebCore stuff.
Still a little buggy
by
kalidasa
·
· Score: 2, Interesting
I'm getting artifacts on the bottom of the frame when I have the text box too close to it. A rendering bug.
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:Still a little buggy
by
goon+america
·
· Score: 3, Funny
Just as a joke, I went to www.whitehouse.gov and reported a rendering error that the person shown was not the right president.
Hope that gave someone a laugh somewhere....
Re:Still a little buggy
by
somethinghollow
·
· Score: 3, Interesting
The only bug I have found so far is that it doesn't run on 10.1.5. Maybe I should "debug" my OS by getting Jaguar. I'd really like to see what all the fuss is about.
Anyone read anything that says why there isn't a release for 10.1.5? What was added in 10.2 that makes 10.1 unusable? After all, the i* applications work on both (don't they)?
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.
Cross-platform web design issue
by
cloudless.net
·
· Score: 4, Interesting
I think Safari will gain popularity quickly, I would like my web pages to look good in that browser. However I only have a Windows box, is there anyway I can see how my web pages look in Safari while I am running Windows?
Re:Cross-platform web design issue
by
Anonymous Coward
·
· Score: 2, Insightful
Yes. Design them for and look at them with a standards-compliant Windows browser, not that piece of shit MSIE.
Re:Cross-platform web design issue
by
cloudless.net
·
· Score: 2, Insightful
Being standards compliant doesn't ensure my design will look right in Safari. Every browser has its own bugs and quirks, CSS2 is an established standard, but even Mozilla can't completely handle it. That's why it is important to test the design in different browsers.
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: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.
Some stuff still needs fixin'
by
phillymjs
·
· Score: 4, Interesting
The only problems I have with Safari are:
1) It does not render the Outlook Web Access from Exchange 2000 properly. This may just be because those Microsoft ass-clowns have coded it specifically for IE, it may not be Safari's fault.
2) One of my larger corporate clients uses some crap web proxy that Safari doesn't like-- http sites load okay, but https sites do not work at all. They don't even try to load. I dunno if there's some authentication issue or what, but I know all my settings are set properly, and everything authenticates fine for http. One of these days perhaps I'll steel myself to talk with one of the corporate help desk script monkeys and see if I can't find out what proxy it is so I can submit a bug report.
~Philly
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.
Either that or they got tired of waiting.
by
Llywelyn
·
· Score: 4, Insightful
It is also possible that they just got sick of waiting for a good, standards-complient web-browser or that they got sick of being so dependent on MS for a decent browser.
Camino and Mozilla weren't quite up to snuf and have serious flaws, as things are; IE was years behind everything else, was too slow, poorly threaded, and had a host of other issues... OmniWeb and Standard Compliance didn't belong in the same sentence--particularly when it came to CSS, and Opera just plain Sucked on the Mac.
The rational choice, particularly for such an important app as a web browser, is in-house development.
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
Gripes about Safari 1.0
by
joelhayhurst
·
· Score: 3, Interesting
First, I'm happy to say that Safari now works with my bank. Yay! But there's still some problems.
Why haven't they addressed the animated GIF problem yet? To see what I'm talking about, check out this example page of the flaw. Only the last instance of an animated GIF is ever animated.
And why'd they remove the minimum font size? On some sites I visit now I see incredibly tiny fonts that are completely illegible. Sure, it might just be a poorly designed site, but it was never a problem in earlier Safari and looks fine in IE and Mozilla.
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
Re:Gripes about Safari 1.0
by
nosferatu-man
·
· Score: 3, Funny
Only the last instance of an animated GIF is ever animated.
My god, this is a problem?
'jfb
-- To spur "enterprise Linux," Big Bang, the distributed two-phase commit.
Re:Gripes about Safari 1.0
by
Erik+K.+Veland
·
· Score: 3, Funny
Why haven't they addressed the animated GIF problem yet? To see what I'm talking about, check out this example page of the flaw. Only the last instance of an animated GIF is ever animated.
That's not a bug, that's a feature!
-- "I tend to think of OS X as Linux with QA and Taste", James Gosling, creator of Java
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
Safari is off to an excellent start
by
King+Babar
·
· Score: 4, Insightful
It really is very impressive, but Jobs is being...cheeky when he claims it is the best browser on any platform. Camino and Mozilla are still competitive, and that's a great thing. Where Safari can do better is in filling in support for features where it is already strong.
So, for example, Safari provides very good support for @media style rules, but (oddly) doesn't support things like the "page-break-before" property or @page {size: landscape}. This is a bit surprising, and I'd like to see Safari reduce the number of surprises in general.
Mozilla can learn from Safari, as well. Safari's bookmark system is better. It's tabbed browsing implementation is nicer. I suspect these features will be adapted into other browsers, and as the competition heats up again (now that the IE giant is sleeping), everybody wins.
--
Babar
Re:Safari is off to an excellent start
by
King+Babar
·
· Score: 2, Interesting
So, for example, Safari provides very good support for @media style rules, but (oddly) doesn't support things like the "page-break-before" property or @page {size: landscape}.
Spoken like a true... well, fucking idiot, actually.
Nobody cares about whether Safari implements all of the fiddly little bits and pieces that make up CSS11 or whatever. What people care about is the user experience.
Uh...frankly *I* don't care about whether Safari implements all of the fiddly little bits of CSS2. Armenian style list items are a nice egalitarian thought, but I don't care if they ever get implemented.
But, believe me, if you had a bunch of undergraduates trying to print out your lecture notes (or a fresh copy of the syllabus, or...) then you would consider page-break-before and size: landscape to be jolly well a part of the user experience. Mozilla gets one of these right but not the other, as does IE. If I could rely on *both* of these working reliably, then life would be much nicer for me (just add a one-liner to my style section to get excellent print out) and for my students.
And, again, one *great* thing about Safari is that it *does* support @media rules really well. So I can make warning text bright red (say) on the screen but switch to bold italic on the print out...stuff that's useful and trivial to do if it's well supported. Doing page-breaks right would add on to a useful feature. Implementing XSLT style sheets in the browser...I'm not so sure.
The one big mega-feature I'd like to see supported, by the way, is SVG. Why? Because a lot of vector graphics look better as...vector graphics. And Illustrator will export stuff that way. But I didn't bring it up at first because SVG alone would be a feature that would justify a whole new major version-number. Page-breaks are a Software Update bug fix.
OK?
--
Babar
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.
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.
Don't ditch Camino just yet...
by
Draconix
·
· Score: 3, Interesting
I tried Safari 1.0 out. Though I admit it has come a long way, it still strikes me as more trouble than it's worth. I ran some tests of it vs. Camino, and Safari actually screwed-up and image render pretty bad. Also, I commonly frequent a couple of CGI chatrooms, and Safari seems to think hitting the enter key should log me out instead of posting a message. I won't be switching any time soon myself.
Also, I'm not too anxious to ditch the Mozilla project yet; I've enjoyed their work for years, and wish Apple had worked with them instead of the makers of Konqueror. Mozilla browsers are the best (or negilibly close) for any platform, from my experience.
-- By reading this you acknowledge that you have read it.
Re:Don't ditch Camino just yet...
by
mgaiman
·
· Score: 3, Interesting
But honestly, isn't it nice to have a choice? I mean, if Apple had gone with gecko, then we'd pretty much only have gecko-based browsers on the mac (neglecting IE--something everyone should do). But this way, two different open source browser efforts are available on OSX.
Personally I've been using safari since tabs were added. Every couple of weeks I download the latest Camino nightly, to see how things are shaping up. I think both are great, safari just seems a little more tuned.
Bug button still there
by
Llywelyn
·
· Score: 2, Informative
Another poster was kind enough to point out to me that you can enable the bug button from inside of the "View" menu.
Re:Still not possible to stop animated gifs
by
glowurm
·
· Score: 2, Interesting
Use these two following Javascripts to get rid of the problem for the most part. Paste the code into a bookmark, and put the bookmark on the bookmark bar. I've got mine set to be first and second on the bar so I can hit command+1 and command+2 to activate them. It deals with most problems with flickering crap for me.
Good Luck!
PS: give the bookmark some short name like [em] and it doesn't take up much space either. Check http://www.macosxhints.com for more tips like this. I got most of this info there.
Don't get 10.2!
by
littleghoti
·
· Score: 2, Insightful
I'd wait for 10.3 if I were you. Get the panther goodness later in the year with all the new stuff, and pay only once.
Safari works on a couple of sites that wouldn't render correctly or missed content entirely. It seems like a lot of debug code is gone, because it runs faster. I'm looking forward to playing with the accompanying web-kit for Cocoa programming.
One thing that bothers the heck out of me is FTP browsing. I'd rather have the choice to mount the server in Finder -- I'd choose NO most of the time and look at FTP in Safari.
-- --Jim (me)
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."
BBC News fixed
by
JonathanBoyd
·
· Score: 2, Interesting
They seemed to have fixed the problem with the BBC News site. Used to be that it would take 5-10 seconds for the newsticker at the top to load, occassioanlly it would corrupt the rest of the page and RAM usage would jump to over 100MB. Now it loads instantly, looks better and only grabs another meg or two.
My impressions, and why I wont switch.
by
saitoh
·
· Score: 2, Interesting
Well, Safari is moving along, although i dont notice much difference between the last beta and this (which in theory meens there shouldn't be too much wrong wtih it), and I also agree that it is a snappy piece of code.
I guess what really prevents me from ditching Camino is that it has many more features that I use. Namely the one critical one being when I open a window, I can open it so it opens under my current window. (very handy for reading/.) Tabbed browsing I can do without (on either browser) but this is something I've grown way too attached to for my own good... ^_^
-- We don't need an "overrated" so much as we need a "you completely missed the parent's point, dumbass..."
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.
Re:What was the default font before?
by
switcha
·
· Score: 4, Interesting
with all due respect, I don't think we are hanging onto serifs because of old rocks. It's all because of readability.
Other factors such as leading and acender/decender height have a huge impact, but none as great as serif/san-serif.
I too, have a degree in printing, and have had textbook after texbook after teacher beat me over the head with case studies in readability.
Especially that slab-serifs (where the serifs and bars have a minimal difference) are kings of readability.
This piece brings up anther interesting factor. Not only are serifs supposedly physically easier to follow in long text, but according to the piece, there is a cultural component as well.
I'm not sure how completely I buy that, as I have read texts citing all sorts of optical testing of jabber text and controls to ensure unfamiliarity. And serif comes out more readable. You can debate whether bylines, captions, or headlines should be serif or san, but try reading Moby Dick in Futura and then after your eyes stop cramping, we'll talk.
-- You know what?... A little club soda *did* get that out!
Tab support is kind of cobbeled
by
Bakafish
·
· Score: 2, Insightful
The problem is that unlike Mozilla based browsers the tabs don't support drag and drop URL's so you aren't able to reuse them. I like to drag links to existing tabs to update them with new information, or drag a URL to the empty tab area to create a new tab.
You can drag links between windows, why not between tabs? At least make the tabs 'spring loaded' or something.
Slashdot Mirror
Oh well. Anyway, I'm getting an iBook soon and look forward to playing around with Safari.
Even 1.0 STILL won't work correctly with my On-line banking!
AARRGGHH!!
I only came here to do two things; kick some ass, and drink some beer...looks like we're almost out of beer.
Nearly perfect timing, too. IE's gone, Safari's here ... out with the old, in with the new.
I'm getting artifacts on the bottom of the frame when I have the text box too close to it. A rendering bug.
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
I think Safari will gain popularity quickly, I would like my web pages to look good in that browser. However I only have a Windows box, is there anyway I can see how my web pages look in Safari while I am running Windows?
The only problems I have with Safari are:
1) It does not render the Outlook Web Access from Exchange 2000 properly. This may just be because those Microsoft ass-clowns have coded it specifically for IE, it may not be Safari's fault.
2) One of my larger corporate clients uses some crap web proxy that Safari doesn't like-- http sites load okay, but https sites do not work at all. They don't even try to load. I dunno if there's some authentication issue or what, but I know all my settings are set properly, and everything authenticates fine for http. One of these days perhaps I'll steel myself to talk with one of the corporate help desk script monkeys and see if I can't find out what proxy it is so I can submit a bug report.
~Philly
It is also possible that they just got sick of waiting for a good, standards-complient web-browser or that they got sick of being so dependent on MS for a decent browser.
Camino and Mozilla weren't quite up to snuf and have serious flaws, as things are; IE was years behind everything else, was too slow, poorly threaded, and had a host of other issues... OmniWeb and Standard Compliance didn't belong in the same sentence--particularly when it came to CSS, and Opera just plain Sucked on the Mac.
The rational choice, particularly for such an important app as a web browser, is in-house development.
Integrate Keynote and LaTeX
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
First, I'm happy to say that Safari now works with my bank. Yay! But there's still some problems.
Why haven't they addressed the animated GIF problem yet? To see what I'm talking about, check out this example page of the flaw. Only the last instance of an animated GIF is ever animated.
And why'd they remove the minimum font size? On some sites I visit now I see incredibly tiny fonts that are completely illegible. Sure, it might just be a poorly designed site, but it was never a problem in earlier Safari and looks fine in IE and Mozilla.
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.
So, for example, Safari provides very good support for @media style rules, but (oddly) doesn't support things like the "page-break-before" property or @page {size: landscape}. This is a bit surprising, and I'd like to see Safari reduce the number of surprises in general.
Mozilla can learn from Safari, as well. Safari's bookmark system is better. It's tabbed browsing implementation is nicer. I suspect these features will be adapted into other browsers, and as the competition heats up again (now that the IE giant is sleeping), everybody wins.
Babar
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.
I tried Safari 1.0 out. Though I admit it has come a long way, it still strikes me as more trouble than it's worth. I ran some tests of it vs. Camino, and Safari actually screwed-up and image render pretty bad. Also, I commonly frequent a couple of CGI chatrooms, and Safari seems to think hitting the enter key should log me out instead of posting a message. I won't be switching any time soon myself.
Also, I'm not too anxious to ditch the Mozilla project yet; I've enjoyed their work for years, and wish Apple had worked with them instead of the makers of Konqueror. Mozilla browsers are the best (or negilibly close) for any platform, from my experience.
By reading this you acknowledge that you have read it.
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
Code 1: Images:
Code 2: Embeds:
Good Luck! PS: give the bookmark some short name like [em] and it doesn't take up much space either. Check http://www.macosxhints.com for more tips like this. I got most of this info there.
I'd wait for 10.3 if I were you. Get the panther goodness later in the year with all the new stuff, and pay only once.
Safari works on a couple of sites that wouldn't render correctly or missed content entirely. It seems like a lot of debug code is gone, because it runs faster. I'm looking forward to playing with the accompanying web-kit for Cocoa programming. One thing that bothers the heck out of me is FTP browsing. I'd rather have the choice to mount the server in Finder -- I'd choose NO most of the time and look at FTP in Safari.
--Jim (me)
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."
They seemed to have fixed the problem with the BBC News site. Used to be that it would take 5-10 seconds for the newsticker at the top to load, occassioanlly it would corrupt the rest of the page and RAM usage would jump to over 100MB. Now it loads instantly, looks better and only grabs another meg or two.
Well, Safari is moving along, although i dont notice much difference between the last beta and this (which in theory meens there shouldn't be too much wrong wtih it), and I also agree that it is a snappy piece of code.
/.) Tabbed browsing I can do without (on either browser) but this is something I've grown way too attached to for my own good... ^_^
I guess what really prevents me from ditching Camino is that it has many more features that I use. Namely the one critical one being when I open a window, I can open it so it opens under my current window. (very handy for reading
We don't need an "overrated" so much as we need a "you completely missed the parent's point, dumbass..."
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.
Other factors such as leading and acender/decender height have a huge impact, but none as great as serif/san-serif.
I too, have a degree in printing, and have had textbook after texbook after teacher beat me over the head with case studies in readability.
Especially that slab-serifs (where the serifs and bars have a minimal difference) are kings of readability.
This piece brings up anther interesting factor. Not only are serifs supposedly physically easier to follow in long text, but according to the piece, there is a cultural component as well.
I'm not sure how completely I buy that, as I have read texts citing all sorts of optical testing of jabber text and controls to ensure unfamiliarity. And serif comes out more readable. You can debate whether bylines, captions, or headlines should be serif or san, but try reading Moby Dick in Futura and then after your eyes stop cramping, we'll talk.
You know what?
The problem is that unlike Mozilla based browsers the tabs don't support drag and drop URL's so you aren't able to reuse them. I like to drag links to existing tabs to update them with new information, or drag a URL to the empty tab area to create a new tab.
You can drag links between windows, why not between tabs? At least make the tabs 'spring loaded' or something.
Anyway, otherwise it is a great little browser.