Slashdot Mirror


Help Make Firefox On Mac Suck Less

bluephone writes "Colin Barrett, one of the new Mac geniuses, and an Adium developer, has posted an entry on his blog offering an open call to all Mac users of Firefox asking them, 'What sucks about Firefox on the Mac?' He says he already knows about and is trying to solve such things as: 'Native Form Widgets (currently scheduled for Firefox 3), Keychain Integration, Firefox should have a Unified toolbar (not completely hopeless, it turns out), Performance...', but he wants to hear what else Mac users want from Firefox. So please, if you're a user of Macs and the interwebs, then RTFA, unclog your tubes, and send him your ideas."

14 of 375 comments (clear)

  1. Camino by daveschroeder · · Score: 4, Insightful

    Isn't this what Camino is for? Like, the very reason for its existence?

    I.e., taking the Mozilla/Gecko codebase, and making a lean, fast browser with Mac widgets, tight Mac OS X integration, Keychain support, and so on?

    I understand the goal of trying to get more Mac-specific functionality into Firefox, but with a fundamentally cross-platform browser, inasmuch as it goes, it's been harder to integrate platform-specific features and functionality into Firefox proper. That's the reason Camino was born: to be a more agile project that is focused on making such a browser for Mac OS X using Mozilla/Gecko. For folks who don't need specific Firefox functionality or Firefox extensions, Camino is already the answer.

    1. Re:Camino by kadat · · Score: 5, Insightful

      Although I'm not a Mac user myself and can't say anything in the matter of usability on Mac OS, I use Firefox on both Windows and Linux mainly because of its extensions as they provide great functionality. Firefox without the plugins is not Firefox anymore, they're one of its most significant features.

    2. Re:Camino by GundamFan · · Score: 4, Insightful

      This is exactly why I love Firefox, no mater what OS I am currently using on a box, I have access to a browser I know how to use. In this way projects like Firefox and OO.org may contribute to the end of desktop OS monopolies.

      --
      I don't give a damn for a man that can only spell a word one way.
      Mark Twain
    3. Re:Camino by daveschroeder · · Score: 4, Insightful

      Uh, Camino is not ghetto. Many people who work on it are the same people who also work on Firefox. The lead Camino developers already work for the Mozilla Foundation. And since its purpose is to take the preexisting Mozilla/Gecko codebase and simply add the Mac OS X-specific functionality, I can't see any logic in your answer: most of what makes up Camino is what you're already using in Firefox.

      And since when do we denigrate open source software as "ghetto" if everyone on the project isn't paid (which is frankly the same as a lot of the work product that goes into Firefox)? How did this even get modded up? Have you ever even used Camino?

    4. Re:Camino by fangorious · · Score: 4, Informative

      ctrl+k puts the cursor in the search bar, ctrl+up/ctrl+down cycles between search engines

    5. Re:Camino by constantnormal · · Score: 4, Insightful

      mod the parent posting up!

      Mr Schroeder is EXACTLY correct -- Camino uses the same Gecko core as Firefox, but eschews the Firefox plugin madness in favor of OS X integration, supporting the OS X Services menu, Keychain, and all the other things that tie an OS X application into the body of OS X.

      If a person wants to use the same browser across Windows, OS X, and Linux -- or has the desire to customize the hell out of it via plugins, then Firefox is the way to go. If a person wants a lean browser that takes advantage of the feature-rich environment of OS X, then Camino is the right answer.

      But if a person wants a lean, fully-integrated-with-OSX browser that looks and behaves like Firefox and supports a zoo of customizing plugins, they're in a world of hurt, as they are looking for the same thing as those seeking a rich, sugary, calorie-laden diet that they can lose weight with.

      The whole notion of Firefox is to make the best cross-platform browser possible. By definition, this means not tying it to the feature set of any particular platform. However, to permit users to tailor their own favorite features into Firefox, they have an excellent plugin system of extensions.

      The idea of Camino is to take the excellent Gecko core from Firefox, and tie it into a particular feature-rich environment (i.e., OS X), making it as fast and powerful as possible. You don't do that by allowing the user to load it down with a bunch of plugins.

      The problem posed by the topic has already been solved. If the Firefox developers want to make it better for OS X users, they should ask the Camino developers (metaphorically across the aisle) what they would like to see changed in Firefox to make Camino development better. Camino IS the end result of optimizing Firefox for OS X.

    6. Re:Camino by Clock+Nova · · Score: 4, Insightful

      Why don't the just add in the plugin architecture to Camino and let the users decide whether or not they want to "load it down" with extensions. Seriously. There's no logic in their decision at all.

      --
      There they were, sitting in the van with all those dials, and the cat was dead. -V. Marchetti, CIA
    7. Re:Camino by Paradise+Pete · · Score: 5, Funny
      And .gov?

      In government there are no shortcuts.

  2. Well... by Megane · · Score: 4, Informative

    I can think of one tiny thing that sucks on Mozilla on Mac... when ever I copy a bunch of text from a window, it puts bleeping CR line breaks in instead of LF line breaks. Unless I fix it first, it makes text editing act a bit wonky.

    --
    #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  3. Its kinda funny. by jellomizer · · Score: 4, Interesting

    I usually use Safari but I don't know why. I have firefox in my dock right next to it. I also tend to get slightly better compatibility with Fire Fox. But... I still use Safari. I think the main reason is probably the bookmarks work better in safari. But I don't really use bookmarks that much. I guess the only feature that I really prefer over Safari that I use over Firefox is RSS I just like Safari RSS Support better then Firefox. If I bookmark an RSS Feed it automatically subscribes me. And there is a search bar right there for me to find info in it. It is not that firefox is bad and there isn't a work around it is not that hard to do a cmd-F (though having the search on the bottom of the window is annoying) It is usually easy to make an app that looks and works good for both Linux and Windows. But for Mac there is a slightly different set of standards. Firefox isn't horrible but if still feels out of place.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  4. Huh? by wandazulu · · Score: 5, Interesting

    I use FF exclusively on both the Mac and Windows, and I think the Mac version works *better* than on Windows...the Mac version doesn't get sluggish after opening and closing a lot of tabs, doesn't gobble up half a gig of ram, and I have never had it just up and quit on me like it does on Windows.

    I find FF on the Mac is also more tolerant of some of the more ... baroque addons; I admit to being an addon junkie and addons that claim to be fully cross-platform crash on Windows while I've never had an addon crash FF on the Mac.

    So, hey, if they want to make FF better, that's awesome, but to me, it's enhancement, not fixing.

  5. to be fair to mozilla... by owlnation · · Score: 4, Informative

    They have significantly improved Firefox on the Mac as time goes on.

    I found I had to be very dedicated to use Firefox 1.5 - that release just plain sucked, especially with regard to stability, favicon use, bookmarks, and I found the search bar crashed the app more often than not.

    However, since v2.0 things have got better, it seems to be overall more stable and they have addressed the favicon issue up to a point. Bookmark control still leaves a lot to be desired. (Though that has room for improvement in the Windows version too - and I know that's being addressed for v3.0).

    I seem to remember reading that for v2.0 they had a deliberate policy of a "Firefox look" across platforms, thus moved away from an OS X looking application. I'm not sure if that is the right decision. Firefox does look odd on a Mac. (And for the inevitable reply that says "but you can use a theme to make it look like OS X" - I'd rather not even try, themes can be very unstable and hog resources.)

    It's a tough market - Safari is a great browser, the only real reason to use Firefox is the extensions (which is a great reason, and the one that keeps me loyal to the Fox. You'll only prise Flashblock and Adblock from my cold dead mouse hand)

  6. UNO makes Firefox look a lot prettier on OS X by spam38 · · Score: 4, Informative

    The way Firefox looked in OS X always kinda bugged me, and in my search for a more OSXish theme, I've found UNO. I'd try to explain what it is, but you'd be better off checking the website: http://gui.interacto.net/. There's also a Firefox theme that pretty much completes the package at http://www.takebacktheweb.org/. Its called "GrApple (UNO)".

  7. Re:Here's a few (more) by MachineShedFred · · Score: 4, Insightful

    Recognize when someone changes the network location, and adjust proxy settings accordingly.

    This bugs the crap out of me, and is the primary reason why Firefox isn't used on my MacBook Pro.

    --
    Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.