Slashdot Mirror
Safari Beta Updated
Jack Kennedy writes "Apple has released Safari 1.0 Beta v51. Unfortunately, Apple don't list what the update addresses; according to Apple, 'this Safari Update is recommended for all Safari users.' Dave Hyatt's Weblog provides a more detailed account of what issues Apple have addressed over the past few days."
I noticed that the new Safari is much more stable. But it still does not allow me to log into my hotmail account. What's up with that?
I noticed it b0rks some shopping carts with a lot of java, namely crystalfontz's cart. Maybe this new build will solve that.
I will now redundantly add my name to the end of my post. You know, in case you forgot me or something.
Safari Beta v51.. now with 10% less Rhinoceros gorings.
Means beta software is expected to have serious problems with it, and that making fun of this fact is neither insightful nor funny.
The bugs I reported haven't been fixed:
* HTTPS doesn't work at all for me over a proxy. I think it is using SSL to talk to the proxy which isn't right. It should connect to the proxy in the clear and then issue a CONNECT and then use SSL. Anybody seen this one?
* "don't use proxy for these hosts/domains" setting is treated as hosts only (so if you put in "foo.com" then you visit "www2.ecommerce.foo.com" the proxy gets used anyway).
* keychain entries of the form "http://host.com:80" are ignored, and it adds its own "http://host.com" entry.
Anybody notice any concrete differences?
Repeat after me
Apple is
Apple was
Apple will
Apple did not (or didn't)
Apple has
learn it
T Money
World Domination with a plastic spoon since 1984
It's nice to see apple updating their beta software - We can only hope to continue (we all must have experienced that long long wait for new features/pest control)
Is this a trend that will continue? - Or is this simply an update that stops Safari eating your first-born or whatever all those bugs did
- WebKitMinimumFixedFontSize
- WebKitMinimumFontSize
Follow the same format as WebKitDefaultFontSize and it will work exactly as you'd expect.OK, I'm not trolling here, it would have been really amazing if Apple had added supports for tabbed browsing in only two days. And I understand they haven't.
I've read somewhere that David Hyatt himself told that the tabs were planned for the final release and that the lack of tabs in current beta's is only due to their deadline. Allegedly, they wouldn't have had time to program tabs support (which is strange since they are working on it for one year now and that Cocoa should make things like adding tabs support quite easy to implement).
Does anyone have real information about that?
Instant Karma's gonna get you, Gonna knock you right on the head (John Lennon, 1970)
We'll kill you if you ever post on Slashdot again.
lol. Reading this five minutes after adding:
/Users/mikehamb/Library/Preferences/com.apple.safa ri.plist;open /Applications/Safari.app'
.bashrc
alias rhino='rm -f
to my
I hereby place the above post in the public domain.
The poster's email address ends in .FM and while I'm not sure what country that is, they probably don't speak english natively - so this is understandable.
What isn't understandable is why a slashdot editor wouldn't have seen the GLARINGLY PAINFUL grammatical error and simply changed "don't" to something proper.
(This comment posted with Safari)
TANSTAAFI: There Ain't No Such Thing As A Free iPod.
slow FPS for Flash still not fixed. This was supposed to be fixed already. Maybe its just not in this release? I just think that is incredibly lame. The most popluar, dynamic tool for delivering web content and its not being properly support wiht Safari. Maybe this is a difficult thing? Not a problem in any other OS X browser. It (Safari) is back on the shelf for me... back to IE. : (
I just noticed something totally cool about Safari. I was browsing espn.com and wanted to hear what Bill Cowher had to say about the penalty at the end of today's game. I clicked on the link for the video stream, and it asked if I wanted Real or Windows Media. First I tried Real, the window it created was a little too big but the plugin came up and worked just fine. Next I thought, what the heck, let's try Windows Media. Note that this plugin has NEVER worked for me in any browser other than IE, for who knows what reason. Anyway, I clicked the stream again and selected Windows Media. Up comes the window, and a sheet drops down that says something like "Safari doesn't know how to use this plugin. However, the program Windows Media Player may be able to handle this file. Wanna give it a try?" I say sure, and *bang* WMP starts up and plays the clip! No more digging through the source and cutting and pasting .asf URLs! Oh happy day!
...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
Rats; I'm still getting failure with what claims to be Beta51. :-( I have the first beta still hanging around, though; is
there some trick to the upgrade I missed?
Babar
I used to think exactly what you think about this. Then after seeing (again) some of the objections to them, I came up with an idea to gain tab-like functionality using ideas already implemented in what you might call "bookmark view" and the (key) idea that the information about existing windows that exists in the "Window" menu really wants to be treated like a collection as well. Check out: my previous post on a different safari thread, and then maybe also a slight tweak designed to bring up the "tab list" separately from other bookmark stuff. In both proposals, you would not have tabs listed across the top of the browser by default, and you would have to hit one keyboard combo (either option-cmd-B or option-cmd-w) to see the "tabs" at all. But after that, this view is *better* than what you get from tabs or the Window menu since it would essentially never have to truncate page titles and would obviously give you space to display URLs.
Again, the basic idea is that the "window list" information could be made more navigable in a form very similar to that for bookmarks or the late, great file selector dialogs that allowed type-ahead on filenames. (I think Safari needs type ahead for links in normal webpages, too. Since type ahead is intuitive when the focus is in the location bar, I don't think it's a big stretch to make the Mozilla-like leap to allowing it when the focus is not on a text entry box of some kind.
The functionality of tabs (rapid navigation to one of the several pages you have open) is preserved, while UI cruft is not required. Please tell me what you think. :-)
Babar
IMHO, there is simply no room for a tray on the side of that window, especially if I want to interact with other programs. I feel that tabs, even though they take up precious vertical space, are a much better MDI (oh how happy I would be if the tab bar could be vertical, running down the left-side of the window...but I feel that the horizontal tab bar is more intuitive to use).
So, while a tray might seem like a great idea for users with high resolution screens, right now it seems like a huge part of Apple's market is laptop users, and unfortunately, our screens just don't have many pixels.
As far as tabs go, I wish Mozilla's tabs were a bit narrower and I wish I could shrink the font of the page titles to gain a few more precious lines back. Currently, I have found (for my browsing style) using the PinBall theme with icon only buttons gives me the most real-estate to work with.
But this is all just my own humble opinion, and I cannot speak for all iBook users. Cheers. :-)
"Empathise with stupidity, and you're halfway to thinking like an idiot." - Iain M. Banks
as we aren't a bunch of 'Anonymous Coward' toting pussys!
The problem with slashdot is that most of its users were bullied and stuffed into lockers as kids!
Essentially all your search query strings become an item in the drawer on the side (whichever you like; Cocoa drawers are ambidextrous. Try collapsing the drawer in mail, and then drag a message to the right, and then to the left... you'll see what I mean.) This approach is comparable to Tabs in functionality, but appearance-wise takes advantage of the fact that tabs work better vertically for most situations, displaying additional information about the query, and offering controls over that query.
A drawer approach in a browser would offer some interesting advantages over the tabs; one could arrange ad-hoc or dynamic collections within one such drawer entry, much in the way iTunes Smart Bookmarks work. For example a 'News' item, 'Blogs' item, etc.
Similar functionality exists using the folder structures in the Safari Bookmark Bar, but the horizontal arrangement does sacrifice some real estate in the UI, as you want as much vertical room as you can get for your browser window, generally speaking. I wouldn't be surprised to see Apple implement a whole history in a drawer though, complete with scaling thumbnails of the pages themselves. (mostly cosmetic, and useless, that last bit - but it'll look damn cool).
If Jesus wants me it knows where to find me.
you can read about tabs all you want, but I'll think i'll switch back to IE or Navigator if can't grab text with Safari soon. Don't you gusy do that? I mean drag en drop, that's what it's all about, no? It looks to me that Apple isn't as focused any more on the ease of use (issues with dock, changing the shortcuts from 10.1 to Jaguar). Don't get me wrong, I love X but Apple needs more consistency.
why do you remove the plist each launch?
I think the "ass hat" is that ring you'd have to sit on after getting gored by the rhino that came out of the safari since it is only a beta. So it's a warning to be careful.
Or they've had to much caffeine to type coherently. One or the other.
R: That voice. Where have I heard that voice before? B: In about 365 other episodes. But I don't know who it is either.
One bug I submitted that has not been address is when clicking on an HREF with a hash, JavaScript doesn't have access to the value, like in this example (shown source intended):
Example
Safari yields an alert that just contains a single "#" character. Other browsers will say "#hash" instead.
A programmer is a machine for converting coffee into code.
Users of build 48 (one of them - there were evidently two) got nuked on two issues:
/tmp disappeared; and
1.
2. all of one's own files disappeared, along with one's home directory. Immense data loss, and not being able to even log in - a major tragedy.
Neither Apple nor Hyatt have dared mention the second issue. That is weak.
The idea of referring to some one as an "ass hat" has been cracking me up all day. Snorting Milk-through-the-nose funny. It's such a double-think sort of joke.
Um that's just the downside of killing pop-ups. Maybe a cooler way of killing pop-ups would be instead to have two more options one is "show pop-ups for 2 seconds then close them" and also an option-click to "show missing pop-ups" so you can see what you missed.
Throughout the Chimera nightly builds, I've been comparing its speed with IE by running non-scientific side-by-side browser tests. Chimera could only occasionally beat IE for loading sites like CNN, MSNBC, or Salon. Safari, on the other hand, beats IE all of the time. My test machines: PowerBook G4/500 and PC with a Celeron 400. It's sad that the Celeron used to beat the G4. It certainly isn't beating it anymore.
I don't, but if it shits itself and corrupts the plist (as happens occasionally), it's nice to have a shell script to remove it instead of manually.
I hereby place the above post in the public domain.
i dl'ed safari and it worked slick...until it crashed--now, everytime i try to launch it, it starts up and then eventually crashes...(i'm using osx 10.2, btw) i dl'ed the supposedly upgraded beta (v51), but same results--also, it looks identical to the first beta (get info on both just says '1.0 beta'). i'd like to report this to apple using their nifty little bug button, but it's kinda hard when the app won't even open up;>
Not only is that an irritation, it has security implications, too.
it means an adornment for the posterior.
ass hat!