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."

19 of 95 comments (clear)

  1. Hrm. by twiztidlojik · · Score: 4, Interesting

    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.
  2. Re:What does this one do? by Anonymous Coward · · Score: 5, Funny

    Safari Beta v51.. now with 10% less Rhinoceros gorings.

  3. Re:Much more stable. by danamania · · Score: 4, Funny

    Hotmail (using both versions, 48 and 51) just tells me I need a javascript enabled browser, after trying to log in - javascript is on, and works elsewhere.

    I can't login to my spam collection anymore!

    dana

  4. Re:Much more stable. by whee · · Score: 5, Informative
    Actually, it appears Microsoft has their own version of the lameness filter. If you first enable the Safari Debug menu with defaults write com.apple.Safari IncludeDebugMenu 1 in Terminal.app, and then change the User Agent to MSIE 6.0, Hotmail will work fine.

    Safari can definately handle Hotmail, but the UA checking is holding it back.

  5. Re:Much more stable. by the+Dragonweaver · · Score: 4, Informative

    Uncheck the "kill popups" box, log in once, and then check that box again. Future logins should not be affected. we've already reported this "bug."

    --
    Actually I am a lab rat in an elaborate plot to take over the world.
  6. Re:Much more stable. by Twirlip+of+the+Mists · · Score: 5, Informative

    Huh, okay I see that now. Here's why I do: type "hotmail.com" in the address bar. Enter user name and password. Get the JavaScript error. Type "hotmail.com" in the address bar again. This time I'm just asked for my password. Enter it. Get right in to my mailbox.

    Try that workaround. Meanwhile, I've put in a bug report on your behalf.

    --

    I write in my journal
  7. hmmm... by Dr.+Awktagon · · Score: 5, Interesting

    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?

    1. Re:hmmm... by fault0 · · Score: 4, Informative

      > Anybody notice any concrete differences?

      Hmm, it does seem to run the CSS tests now (and does pretty well)

  8. minimum font size support! by frankie · · Score: 5, Informative
    Blatantly cribbed from MacOSXHints.com. Edit the file ~/Library/Preferences/com.apple.Safari.plist and add two new siblings to the XML tree:
    • WebKitMinimumFixedFontSize
    • WebKitMinimumFontSize
    Follow the same format as WebKitDefaultFontSize and it will work exactly as you'd expect.
  9. Unfortunately still no tabs by Ma�djeurtam · · Score: 4, Interesting

    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)
    1. Re:Unfortunately still no tabs by stux · · Score: 4, Informative

      That's funny...

      I heard that he categorically said "no tabs" ;)

      --

      ---
      Live Long & Prosper \\//_
      CYA STUX =`B^) 'da Captain,
      Jedi & Last *-fytr
    2. Re:Unfortunately still no tabs by babbage · · Score: 5, Insightful
      Here's an idea: let's re-evaluate what you *really* want the software to do here. Is it really the case that you need tabs, or can it more accurately be said that you just want some form of a multiple document interface [MDI]. If the latter is correct -- and for me, it is -- then are tabs (as implemented in the Gecko family of browsers) the best or only way to do this? Or are there other, possibly better ways to get to the same goal?

      It occurs to me that a better -- and arguably more "Cocoa-ish" -- way to present this would be a tray interface, like what you see in Mail.app. Seen this way, you could have a hierarchy of widgets in the tray, including:

      • currently open pages (the tabs, as available in Mozilla etc)
      • bookmarked links & folders of links
      • history links
      • "scrapbook" page[s]?

      If presented this way, you could browse open documents and bookmarks much as you can browse mail folders in Mail.app. If items in the tray could be browsed with "flippy triangles" (like in the Finder's list view), then you could zoom in on different kinds of URLs quickly. Plus, having a tray interface might even buy you enough screen real estate that you could even have thumbnail versions of some or all pages in the collection. Neat, huh?

      Personally, I agree with everyone that's asking for tabbed browsing, but only to the extent that I think that the web is easier to browse in a MDI style. But the more I think about this tray idea, the less I think that simple tabs is the best way to present this information. Trays. They're IMO the coolest & most innovative part of the Aqua interface, and they really aren't implemented all that often. This seems to me like a perfect place to introduce a tray interface, and if Apple decides to add a MDI option to Safari, my hope is that this is how they'll implement it.

      If you agree that this is a good idea, please do as I've done and submit the idea as feedback to Apple with Safari's bug reporter widget, or by using the bug reporter on Apple's site (sorry, I forget the url offhand). Now is the time to let them know what features you would hope for... :)

    3. Re:Unfortunately still no tabs by babbage · · Score: 4, Informative
      Skimming your linked post (sorry, will read it in more detail after this), I don't think we're describing quite the same thing here. What I'm referring to as trays should more accurately have been referred to as drawers, as that's the term that the Apple documentation seems to use. Out of habit, I use the terms 'tray' and 'drawer' more or less interchangeably, but I'm realizing now that searching for 'tray' interface elements isn't turning up many hits, so maybe this usage isn't as standard or common as I thought.

      In any case, in the Aqua interface, trays are a specific & unambiguous interface style that for whatever reason hasn't been used very often so far. The best example I can think of from one of the "core" applications is Mail.app, for which there is a screenshot at Apple's site. The other big application I can think of right now is Omniweb, which uses a drawer to organize bookmarks. (I'm not an Omniweb user, so I wasn't aware of that until searching for this post :). Of freeware apps that I use regularly, the best example I can think of is (the very slick) MacJournal, which uses two trays -- one to present a list of journals, the other to present entries within a particular journal (for example).

      Now that I poke around a bit, the best critical reviews of the tray interface I can find so far are this MacEdition review and this Oreillynet tutorial. (John Siracusa also wrote some excellent OSX reviews for Ars Technica, but I can't find a section that focuses on drawers in particular.)

      But the authoritative reference -- which unfortunately doesn't seem to have screenshots to go along with the prose -- is the Apple MacOS X Human Interface Guidelines:

      Drawers are a special window type, found only in Mac OS X. They are child windows--which slide out from a parent window--that users can open or close (show or hide) while the parent window is open. These windows should be used for tools or controls that are closely associated with the parent window and frequently accessed, but do not need to be visible all the time. For example, Mail uses a drawer to provide access to the user's mailboxes.

      So while this isn't incompatible with what you're asking for, it looks to me like it's not quite the same thing. This is an existing toolkit that could be called on by any Cocoa or Carbon application, and it seems to me like this is a perfect example of where best to apply it.

  10. The biggest change by andfarm · · Score: 5, Informative
    Apple claims to have fixed that nasty bug with wiped $HOME directories and deleted /tmp->/private/tmp links. Reason enough for me to download it.

    (This comment posted with Safari)

    --

    TANSTAAFI: There Ain't No Such Thing As A Free iPod.

    1. Re:The biggest change by Lars+T. · · Score: 4, Funny

      Well, just don't use Safari to download it ;-)

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

  11. Excellent feature by yomegaman · · Score: 4, Informative

    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.
  12. Possible better answer to the tabs problem by King+Babar · · Score: 4, Insightful
    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 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

  13. Re:.fm by Toraz+Chryx · · Score: 4, Funny

    As an Englishman myself, I have this to say.

    It's our language and we can butcher it any way we see fit.

    So there! :p

  14. Re:.fm by kalidasa · · Score: 5, Informative

    All dialects, including those who developed in England, are incorrect. Most dialectic differences were develloped by illiterate people. There is a correct way to use plurals in English which is well-documented, and it does not matter where you are from.

    This is misinformation. All dialects are correct, in that all dialects are self consistent with their own sytaxes and vocabularies. One can speak of the standard dialects, for instance, Received Standard Southern British, which is the canonical British dialect for public discourse, and Standard American English, which is the canonical American dialect for public discourse, or . Another widely used dialect in the United States is African-American Vernacular English, which is sometimes called by linguists Standard African American English, and politically sometimes called "ebonics" and distinguished as a different language by well-meaning idiots who have no background in linguistics.

    If one wishes to take part in public discourse, particularly in print, and especially "learned" discourse, it is necessary to learn one of the standard dialects, and it is helpful to learn more than one (e.g., both the American and British standard dialects). If one wishes to converse with persons from other regions that speak English and be sure to understand them, it is helpful to know something about the non-standard dialects which we all use (for instance, The Jargon File is in part a dictionary of a particular non-standard dialect used by self-identified "hackers," and like all dialects, its use is part of that process of self-identification).

    One's speech can be incorrect with reference to a particular dialect; for example, one who speaks of a cracker as a "hacker" is not speaking in correct hacker dialect, and is thus identifying himself (or herself) as a poser (i.e., is unintentionally emphasizing an false affectation). Thus one can, in the schools (one of whose primary purposes is the teaching of the local standard dialect), speak of right or wrong use of plurals, in reference to that standard dialect. But one cannot apply the rules from one dialect to others and necessarily identify what are right or wrong uses correctly. Indeed, this is a case in which the American and British standard dialects differ; if one says "Apple is," one is identifying oneself as an American or a wannabee; if one says "Apple are," one is identifying oneself as a Brit/Canadian/etc. (I think this is the usage in the various Commonwealth countries) or a Brit wannabee.

    Here's an excellent thread on a linguists list that talks a little bit about prestige or canonical dialects and standards.

    I leave the enumeration of the number of different dialects intentionally used in this posting as an exercise to the reader, though I point out that it is an exercise intended to show how shifts in dialect can change one's sense of the "identity" of a writer/speaker.