Slashdot Mirror


A New Look For Firefox

ben writes "Regular users of Mozilla Firefox may be interested to know a new default theme is planned for 0.9 in preparation for the road to 1.0. 0.9 will also feature new improved theme and extension management, which will make it easy to make Firefox look the way you want it to."

102 of 416 comments (clear)

  1. How about... by G-funk · · Score: 5, Insightful

    ...They leave everything as it is, and fix the resource leak in windows? It's hard to try and convince people to switch to my browser when I have to "end process tree" the thing once a day.

    --
    Send lawyers, guns, and money!
    1. Re:How about... by Anonymous Coward · · Score: 3, Interesting

      eh? i use FF loads and don't have to do that, ever. could it be one of your extensions or sommat?

    2. Re:How about... by linuxci · · Score: 5, Insightful

      Well remember the people who design themes aren't the same sort of people who can fix resource leaks!

      Also have you got a bug number for this? I've not had any major problems with Mozilla or Firefox for ages.

    3. Re:How about... by hattig · · Score: 5, Insightful

      Definitely. It looks fine at the moment, but that resource leak is the biggest annoyance. Especially when everything stops responding because Firefox running as the only application starts paging on a 512MB machine.

    4. Re:How about... by Raven42rac · · Score: 3, Insightful

      First of all, it is a free browser, they have no obligation to fix anything. Buy a shirt, then whine. Second, if they are having legal issues with their art, then to ensure the continued existence of their browser, or else they will have no chance to fix the bugs. On another note, I have never had any problems with the browser from Phoenix to Firefox. Are you using the nightly builds or the official release. If you are using the nightly release, be careful what you wish for.

      --
      I hate sigs.
    5. Re:How about... by sgarrity · · Score: 2, Informative

      Actually, a reader pointed out only this morning that the MSNBC This Week in Pictures feature now does work in Firefox.

    6. Re:How about... by xandroid · · Score: 4, Informative

      A thread I stumbled upon at MozillaZine mentioned that these resource issues won't be fixed in 0.9, or even 1.0.

      (Not sure if this is gospel truth, but I sure hope not... kill -9 firefox is getting old...)

      --
      $ echo "ceci n'est pas une pipe" | sed -Ee 's/(eci n|pas )//g'
    7. Re:How about... by thakadu · · Score: 3, Insightful

      I am sorry that you are experiencing these leaks as I am fortunate enough not to have had them yet. I also am running a 512MB machine (WinXP) and I have almost always got at least 3 FireFox tabs open and I very seldom reboot. The one thing I don't have is the Flash plugin. Could it be this causing the leaks you are experiencing? The only instability problems I currently have are:
      1) Bookmark icons on the bookmarks toolbar seam to come and go as they please. (Also happens in IE)
      2) Text entered in a form field before the page is fully loaded often gets blanked out once the page has completed loading. (Not in IE)
      Otherwise I have found 0.8 to be at least as stable as IE and certainly much snappier.
      Good luck.

    8. Re:How about... by TheSpoom · · Score: 2, Informative

      I have only ever experienced this with Tabbrowser Extensions installed. Once I disabled it, Firefox was VERY stable again. Could this be the same with your issue?

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    9. Re:How about... by nwbvt · · Score: 2, Informative

      Yeah, I have had some problems with the Tab Browser Extensions plugin but I havn't seen this problem with the browser itself.

      --
      Mathematics is made of 50 percent formulas, 50 percent proofs, and 50 percent imagination.
  2. I liked the old look by linuxci · · Score: 4, Interesting

    I did prefer the old look, but then again the new one hasn't been finalised yet and is still under active development (it's been checked in but not enabled yet).

    Whatever the case, 0.9 will be an excellent release and well worth trying. However, please remember this release will have some major new features (better extension/theme management, migration of prefs from other browsers such as IE, Netscape and Opera) and then focus will be on polish and stability up to a successful 1.0 release.

    1. Re:I liked the old look by Conor+Turton · · Score: 5, Informative
      The preferences importing from Opera works extremely well. In fact I wasn't aware it was there, installed FF 0.9 and fired it up for the first time to set it up just to find it loading up my homepage and my Opera bookmarks were all there.

      A welcome suprise and it means I can get shut of my 3rd party bookmark convertor.

      --
      Conor "You're not married,you haven't got a girlfriend and you've never seen Star Trek? Good Lord!" - Patrick Stewart
  3. Thunderbird? by mccalli · · Score: 5, Interesting
    One reason given is for consistency across platform. I agree with this, but part of the 'platform' is the other software you're likely to use with it. In my case and I suspect in many others, that means Thunderbird.

    Will Thunderbird be following suite and changing default theme too?

    Cheers,
    Ian

  4. Definately a bad choice on the part of the devs by Xshare · · Score: 5, Insightful

    Qute was a great Default theme. It looked great as a default theme, and really made switchers from IE feel comfortable. This new theme just doesnt fit in Windows or Linux... it looks good for OSX, but just not in other OSes.

    1. Re:Definately a bad choice on the part of the devs by Jedbro · · Score: 2, Informative

      Agreed. One of the issues was the license for the grafics, the author has stated he would be willing to change it for mozilla.org.

      While the new theme isn't *bad*, it is not nearly as profesional as QUTE is, and a terrible first impression for new users who are coming off of IE.

      Sad, sad, sad. Wish this could have been discussed first like in the old days (pheonix).

    2. Re:Definately a bad choice on the part of the devs by igrp · · Score: 4, Interesting
      I agree. Most people I introduced to Mozilla were impressed by two features: the pop-up blocker and its feeling. Many remarked that it just felt "right". That's one of the biggest compliments you can pay to a UI designer: if the user doesn't feel that there's a transition period and can get started right away then you've done something right.

      Personally, I'm more of an "I don't care how it looks as long as it works" guy but I agree that the Qute theme looks great and I always felt comfortable using it. I guess variety is a good thing but I'd much rather see them sort out their differences and stick with Qute.

    3. Re:Definately a bad choice on the part of the devs by Xshare · · Score: 5, Insightful

      First off: That's not the new skin: This is. Second:Exactly. You have been using this skin. You know how to change a skin. Hell, you know what a skin is. You are also a reader of slashdot. That already means that you most likely are an advanced computer user, prolly use linux at times, and etc. Most people aren't. The people who we want to convert from MSIE don't like change. They don't want to go into the skinning thing and get a new skin. It's too complicated. First impressions are also crucial, and most "new users" would see this new skin as alien to them, and they won't want to go through the trouble of changing it, and will just slump back to IE. Just my take on things.

    4. Re:Definately a bad choice on the part of the devs by Xshare · · Score: 2, Insightful

      I'm not. I'm pushing Qute. Qute looks perfect. It's natural to both users of IE and those who aren't. Thats what we need. Not something thats only natural to those who aren't. Hell, not something that's downright ugly and noone likes.

    5. Re:Definately a bad choice on the part of the devs by j7953 · · Score: 4, Insightful
      Qute was a great Default theme. It looked great as a default theme, and really made switchers from IE feel comfortable.

      I agree. Replacing this comfortable feeling with a uniform cross-platform look is a stupid idea. Who benefits from a uniform cross-platform look, anyway? Most computer users use only a single platform. They probably don't care at all how the browser looks on some other platform (hell, many don't even know that there are other platforms), but they do care if it looks like it was designed for the platform they use.

      People who use multiple platforms are likely to be experienced computer users anyway, so if they want a uniform look, they'll probably be able to install whatever theme they prefer on all the platforms they use.

      --
      Sig (appended to the end of comments I post, 54 chars)
  5. If you want to take market share by Anonymous Coward · · Score: 5, Insightful

    in the browser market, you'd be looking to take it from Internet Explorer (duh). That's Internet Explorer on Windows ... not the Mac. I think that it is important to have a default theme that makes it easy for the mums and dads to identify with (because they are not likely to change it). I think the current default theme does this and the proposed change is a mistake. But what do I know?

  6. Re:The new theme by linuxci · · Score: 4, Informative

    This is not informative. That's not the new theme. The article at the top points to the thread with the discussion about the new theme.

    This is a port of the Mac Pinstripe theme, although the new theme based on Pinstripe but called Winstripe (the GNOME version is called GNOMEstripe - not Linstripe!) I assume these names won't be used in the finished product though.

    Anyway back on track, although Winstripe will be similar to Pinstripe the icons will look more Windows like and therefore not a total Mac lookalike.

  7. Why bother? by Safety+Cap · · Score: 3, Insightful

    The important things like fixing the preferences, the weird, fatal bugs can wait! We want fun eye candy!!!

    --
    Yeah, right.
    1. Re:Why bother? by linuxci · · Score: 4, Informative

      I've just had a look at the bugs mentioned and they're both being worked on. Therefore it's unlikely you'll see them when 1.0 comes out. However, like I said previously, the type of person who can design a good theme is unlikely to be able to help with the other bugs

    2. Re:Why bother? by irokitt · · Score: 2, Insightful

      Well, in my experience, they key to getting software to be accepted in the wild world out there is the way it looks, not the performance or reliability. After all, look at IE. When a friend of mine switched his families browser to Firefox, the biggest beef was "it looks hokey" (he hadn't installed any of the pretty themes). So perhaps the dev team has realized that the development path should include parallel development on the eye candy, instead waiting until everything else is done to work on the interface.

      --
      If my answers frighten you, stop asking scary questions.
  8. opera vs firefox? by zlel · · Score: 2, Informative

    Just tried firefox this afternoon - but switched back to Opera. Am I trying the wrong thing, or does firefox not expose as may options as opera? I wanna be able to do stuff like set my default encoding, browser id, source viewer n stuff like that... without recompling of course...

    1. Re:opera vs firefox? by pmjordan · · Score: 2, Insightful

      Some people prefer FireFox, some prefer Opera. It's really a matter of opinion. I'm tempted to say that for your average end-user, FireFox is the better choice, and for many power users, installing lots of plugins is the way to go.

      Personally, I agree with you, I've been a happy Opera user for years. That doesn't mean that FireFox should be more like Opera, it's just a different approach.

    2. Re:opera vs firefox? by elFarto+the+2nd · · Score: 5, Interesting

      May I suggest you fire up Firefox again, and type

      about:config
      into the address bar and hit enter.

      More options than you could shake a very large stick at

      Also, Character Encoding is in the view menu.

      Regards
      elFarto
    3. Re:opera vs firefox? by Pahalial · · Score: 2, Informative

      Extensions, my friend. For example, there's a user agent switcher that you can customize. there's also a lot more on that page of course, and for the other stuff there's the about:config mentioned in another reply.

      --
      Stuff.
  9. And to celebrate by m00nun1t · · Score: 4, Funny

    They are changing the name!

    It's now known as ThunderFox.

  10. Yay by W2k · · Score: 4, Insightful

    This is why I like open source software development. Just look at that forum thread. Inside a company like IBM or Microsoft, a debate like this would be kept covered up out of PR fears. Open source developers more often than not do not give a shit about PR (which is a good thing), they just want to make the best possible program. They also don't have to be afraid of losing their jobs, getting their salaries lowered, or whatnot. So we get to see the nitty gritty details of intra-project disputes and arguments from the front row, even silly things like what theme ships with Firefox as the default.

    Gotta love it.

    --
    Quality, performance, value; you get only two, and you don't always get to pick.
    1. Re:Yay by geeber · · Score: 3, Insightful

      This forum thread was started by taking a private email and posting to a public forum without the author's permission. This is not the sort of behavior that should be celebrated, whether it is done inside a private company or in an open source community. It is a serious violation of ettiquite.

    2. Re:Yay by eyeye · · Score: 4, Informative

      Firefox devs make their decisions (e.g name changes!) behind closed doors and the first you know about it is when they have already made the change.

      I am glad he released this info.

      --
      Bush and Blair ate my sig!
  11. Fuck the Mozilla devs by Fnkmaster · · Score: 5, Interesting
    Sorry to sound like a prick, but some of the lead Mozilla developers have turned into incredibly unresponsive pricks that don't know how to delegate and assign authority properly. I respect their hard work immensely, but their attitude and arrogance on certain issues continues to mystify me. Look at this new theme at the top of this thread. This is beyond atrocious. This is because the Mozilla devs don't know how to resolve differences with other people, and they REPEATEDLY have shown a complete indifference to aesthetic issues in the browser and an unwillingness to make use of the talents of the many artists out there who would be very willing to help create good splashscreens, icons and so on, a rather critical part of a mass market desktop application that we want people to adopt (in the interests of a more secure, standards-compliant web).


    Yes, Arvid Axelsson, the author of the current default theme (Qute), may have a bit of an ego himself, and may have been reluctant to freely license his artwork under the same MPL terms as the Mozilla codebase. But he's a reasonable person, and he's indicated he's willing to compromise and do a Free license that works for the Mozilla team, because he wants to make sure that Firefox succeeds, and has the best, most aesthetically pleasing look and feel possible.


    For God's FUCKING sake you egomaniacs (and anybody who has followed some of these discussions over the last few years knows this is true - see the splashscreen debacle in Bugzilla, the many UI layout discussions, and the naming debacles for examples), we are relying on you and the excellent browser you have created and maintained. We respect immensely all the hard work the Mozilla and Firefox core developers have done, but their lackadaisical attitude towards branding of their product (Phoenix/Firebird/Firefox?), the terrible aesthetics of the splashscreens and icon sets they keep putting back in are just unacceptable. Qute was the best thing that ever happened to Firefox and the Mozilla project - compare to the awful looking old versions of the Mozilla browser - ugh.


    You are the developers and project leaders of a critical mass-market product. If there is truly an unresolvable licensing issue with the current icons and their author is unwilling to compromise, come out and tell us, and assign a group of artists or other aesthetically inclined technology professionals to consider submissions for a new default. Realize that your contributions, while critical, do not need to include drawing shitty icons or making terrible off-the-cuff aesthetic decisions that have a negative impact on the adoption of a critical product for the entire Internet's wellbeing.

    1. Re:Fuck the Mozilla devs by linuxci · · Score: 4, Insightful
      The problem is when you debate every little detail to death you get a browser like the Mozilla suite which progressed relatively slowly because everything was a committee decision.

      Yes I do think this could have been handled a *lot* better because Arvid but a lot of work into this excellent theme and now is word will be getting a lot less attention as it'll now just be a downloadable theme on update.mozilla.org

      Also as you can see from the forum thread mentioned in the original article you can see the information process wasn't the best.

      However, ultimately difficult decisions have to be made and they can't satisfy everyone all of the time.

      If you look at the original charter for m/b, Phoenix, Firebird, Firefox you'll see that they intended from the very beginning to have only a small group of people making the decisions.

      To quote:
      The size of the team working on the trunk is one of the many reasons that development on the trunk is so slow. We feel that fewer dependencies (no marketing constraints), faster innovation (no UI committees), and more freedom to experiment (no backwards compatibility requirements) will lead to a better end product.

    2. Re:Fuck the Mozilla devs by Fnkmaster · · Score: 4, Insightful
      Those difficult decisions should not be made by Ben Goodger. I'm sure he's a great, stand-up guy. I've worked with engineers like him before - their code may be fabulous, but their sense of aesthetics is fundamentally broken. I support the idea of a small group *of artists and UI designers* making UI decisions, and a group with some marketing experience to make branding decisions.


      I've managed plenty of software development teams before, and you just don't assign any random engineer to make important UI decisions. Some people have the talent for this and some don't. It's part aesthetics, part usability, part style. Very important stuff, and not something you learn getting a computer science degree, hacking Unix, writing HTML rendering engines and so on.

    3. Re:Fuck the Mozilla devs by bogie · · Score: 4, Interesting

      This is just indicitive of the way the entire Phoenix/Firefox project has been handled from day one on issues that actual users are interested in. They devs simple are not interested in taking in and responding to feedback from users on issues that users really care about like aesthetics. Look at the bugzilla voting system for an example. No matter how many votes a bug gets the devs could care less. Yes at some point someone needs to step in and say "This is how its going to be", but jeez at least try to make it look like you value the opinion of the people who have been bug testing and promoting *zilla for years and years now.

      I still use Firefox but I don't particpate anymore. I don't file bugs and I don't post in the forums. If the developers are going to continue to not pay attention to the users then they are losing IMHO their greatest strength outside the actual merit of the products themselves.

      Call me a drama queen. Explain how I'm wrong. But don't discount the fact that many people right or wrong feel the same way as I do.

      --
      If you wanna get rich, you know that payback is a bitch
    4. Re:Fuck the Mozilla devs by Anonymous Coward · · Score: 2, Insightful

      Since AOL spun off Mozilla it's been the fastest developing major scale Open Source project in the world, and immensely popular. It's a ridiculous argument to make that because 'bogie' didn't get personalized service their development model is a failure. If you think I'm wrong, please try the same thing with Microsoft, Apple, or Sun and report back on your success. Damn, where do these people get off thinking the open source development model has some equivalency to ordering re-fills on ice tea at the local diner?

    5. Re:Fuck the Mozilla devs by Malc · · Score: 2, Interesting

      You're right, and it's been going on for years. Just look at the duplicating/cloning new window bug. People have been begging for it for years because they like the way IE does it. The devs didn't like that feature and acted like pricks about it. I lost interest in even considering getting involved. These days you can get the functionality via the excellent Tabbrowser extension... I just wish it were implemented in the core code base with an option to enable or disable it. Oh well, and you wonder why Apple really chose KHTML... I wouldn't want to have to deal with the Mozilla team.

  12. Re:Nope by FuzzyDaddy · · Score: 2, Informative
    This issue is fixed here, as well as mentioned on the home page for firefox.

    --
    It's not wasting time, I'm educating myself.
  13. Already slashdotted... by Momo_CCCP · · Score: 2, Insightful

    ...poor forum server is screaming...
    Consistency across platforms or within platforms is quite a non-issue to us KDE users : the Plastik and Keramik themes for Mozilla and Firefox are beautifully integrated in the KDE desktop, so whatever the default themes becomes, we'll still be happy.
    As long as skinning is avaible, everybody should be happy.

  14. Did they fix the Cancel/Ok buttons? by GodWasAnAlien · · Score: 4, Funny

    Can I configure Firefox back to the sane Ok/Cancel button order?

    No or Yes?

    1. Re:Did they fix the Cancel/Ok buttons? by linuxci · · Score: 3, Informative

      That order is only in Mac/Linux builds.

      The reason for it in Mac is because all apps should be that way due to the UI guidelines.

      As for Linux apparently it's in the GNOME UI guidelines. However, I rarely use any other GNOME apps in Linux, most things I do are either in browser or in a terminal window - therefore the button ordering is frustrating for me when I'm in Linux because I switch between Windows and Linux more than Linux and Mac.

      But technically they're doing the right thing - although ideally it'd only display in that order if you're actually using GNOME.

    2. Re:Did they fix the Cancel/Ok buttons? by marq00z · · Score: 5, Informative
      It's not a bug, it's a feature. The Cancel|OK order appears only in Linux and Mac OS X and it's done this way to be compliant with Gnome and Apple Human Interface Guidelines. If you want to have the Windows-like OK|Cancel order, just add these lines to your userChrome.css in your .firefox//xxxxxx.slt/chrome directory:
      .dialog-button-box {
      -moz-box-direction: reverse;
      -moz-box-pack: center;
      }

      .dialog-button-box spacer {
      display: none !important;
      }
    3. Re:Did they fix the Cancel/Ok buttons? by FooBarWidget · · Score: 2, Interesting

      Ok/Cancel or Cancel/OK buttons are fundamentally flawed, and outdated. Both GNOME and KDE use action verbs, just like MacOS X. So instead ok Cancel/OK you can Discard/Save or something.

    4. Re:Did they fix the Cancel/Ok buttons? by tepples · · Score: 2, Insightful

      KDE has been using that standard longer

      Calendar priority examples are bad examples. Mac OS has used (Cancel)(OK) since January 1984.

    5. Re:Did they fix the Cancel/Ok buttons? by damiam · · Score: 4, Insightful
      No, the decision is because they did think about it. Cancel/OK makes more sense and is fundamentally easier to use than OK/Cancel. That's why Apple uses it.

      It'd be nice if Firefox could detect KDE and switch its button order. However, as Firefox is written in GTK and KDE already has its own non-Gecko browser, probably most of the Firefox developers aren't KDE users and don't care. If you do care, go ahead and code it.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
  15. You need a bigger "but" next time by Dano · · Score: 2, Interesting

    "..We respect immensely all the hard work the Mozilla and Firefox core developers have done, but.."

    Read your own subject line and then tell me during which part of your response you were respectful of them and their work.

    1. Re:You need a bigger "but" next time by Fnkmaster · · Score: 4, Informative
      I've spent a lot of time on the Mozillazine forums and so have many others who've contributed code, artwork, testing and hundreds upon hundreds of hours of their time. I am talking here about the core developers from Mozilla.org who have actively displayed their arrogance repeatedly to the rest of the community. In particular, I think Ben Goodger has stood out as a tremendous prick. In fact, my original post said "Fuck Ben Goodger" in the title, but I decided it was too much of an ad hominem, when many of the others have stood up far too strongly for Goodger.


      Ben Goodger is the strongest anti-advocate for Mozilla I have ever seen. There are hundreds of other developers who have contributed lots of code to the original Mozilla project and the Firefox codebase. Many of these are great people who have quietly contributed tens of thousands of hours of their work over the years to the community. And those people I respect immensely. The ones who insist on repeatedly driving rifts through and disrespecting the fabulous community of Mozilla supporters that have evangelized their product and fought for a better, more standards-compliant internet everywhere else have been done a tremendous disservice to the rest of the Internet, and I have simply lost my respect for them.

    2. Re:You need a bigger "but" next time by STrinity · · Score: 3, Interesting

      I think the most telling thing about Goodger is that he absolutely hates TBE, probably the most popular extension out there, because it makes drastic alterations to the code, but he's made no effort to change Firefox so that TBE would be unnecessary.

      --
      Les Miserables Volume 1 now up with my reading of
    3. Re:You need a bigger "but" next time by stewby18 · · Score: 2, Insightful

      You are clearly talking about a larger issue, which I can't really speak to, but I can definitely say that the thread you linked to does *not* support your case.

      I read it through, and here's what I saw:
      1) A professional email from Ben Gooder saying that Firefox was taking a new direction due to a combination of licencing and UI considerations
      2) A less-than-polite response from the Qute designer, with both the original and the reply posted to a public forum in violation of basic decency
      3) A lot of ignorant flaming of the decision and back-seat driving from people who were not privy to the details of the decision and ignored what they were told about it by Ben Gooder's follow-up post. Interestingly, the people doing said flaming all seemed coincidentally to prefer the Qute theme.
      4) Many people who either didn't like Qute or were reserving judgement one way or the other until they had time to make an informed decision based on the complete theme and actual use.
      5) The Qute fanatics almost exclusively ignoring the people in 4) and claiming that everyone likes Qute better, and that ignoring "the preferences of the end users" was completely against what Firefox should be about (I'll leave the hypocricy in that as an excercise for the reader).

      I certainly did see a lot of disrespect in that thread, but it was all *toward* Ben Gooder, and not *by* him. After reading that thread, what I'm left with is a lack of respect for people who lash out ignorantly and disrespectfully against someone who spends a whole lot of time working on a browser that they all use and enjoy.

    4. Re:You need a bigger "but" next time by STrinity · · Score: 2, Informative

      Oh, come on. TBE's context menus are stupidly huge.

      And 100% customizable. Tab->Edit Context Menu

      Personally I wish Firefox had a similar option so I could get rid of useless options like "Send Link" and "Copy Link Location" without having to edit userChrome.css.

      --
      Les Miserables Volume 1 now up with my reading of
  16. Theme choice... by Epistax · · Score: 4, Insightful

    Now I know you can just download themes to your heart's content. I'm using a tiny theme because that's the way I like it. However there's no reason not to have several default themes to choose from at install time. I would suggest the themes be "Default", "Internet Explorer", "Netscape", "Opera" and perhaps a Macish theme. As long as it is explained that this is simply the look and feel and has no real functionality differences (explained in a calm and simple manner), things should be less scary. Previous posters are absolutely right-- the more different it looks, the more scared the user will be, even if everything is in exactly the same place.

  17. Re:And what was Firefix was for, again ?? by linuxci · · Score: 4, Informative

    Firefox was *supposed* to be a *fast* lean-and-mean browser. One reason was given that bundling IE with OS works because people are too lazy to download another browser. That gap WIDENS as the download size increases. Already Firefox is 10+ MB!!!!


    Don't be such a troll. The download size for Firefox hasn't been anywhere near 10 meg (except perhaps before they stripped out all the app suite stuff).


    If you look at the latest branch builds you'll see that the current download is below 5 meg on Windows.

  18. HCI anyone?? by the_true_cirrus · · Score: 5, Interesting

    Why oh why do they want cross platform uniformity??

    One of the most basic principles of human-computer interaction is consistency. Windows users expect to see Windows-like apps, Mac OS X ppl expect native OS X looking apps and likewise for GNOME, KDE and whatever else.

    Anything that breaks that (for example an OS X app that looks and/or behaves like a Windows app goes against the user's expections. And ultimately that makes the app harder for them to use and hence less appealing.

    Granted there is a lot of similarity between the various desktop environments but they do each also have their own quirks. For example OS X apps have the toolbar along the top of the screen (not part of the app window) and have that little window-resizing thing in the bottom-right corner of a window (not part of the window's border). GNOME and KDE generally have different standard back, forward, reload etc icons for buttons that all apps should use rather than their own.

    If you make Firefox look the same on every platform you will be breaking such little quirks and conventions on some (possibly all) platforms and the users will suffer.

    I say make a different, native looking (and feeling) theme for each major platform and ship it as the default for that platform!

    As for branding - you've got the name, you've got the firefox icon - they stay the same on every platform - surely that's all that's needed.

    Personally I think that's a good thing too. I for one perceive it as really annoying and intrusive when I install an app that insists on planting it's icons all over my desktop, installing a pointless system tray icon and making itself the default player/browser/whatever (eg RealPlayer or QuickTime on Windows) - it feels like I get the branding forced down my throat and that does NOT make me a happy user! Apps that don't feel the need to do that are a breath of fresh air and it would be a real shame for Firefox to go down the road of excessive branding.

    1. Re:HCI anyone?? by per11 · · Score: 2, Insightful

      If I wanted Firefox to look the same on all platforms, I would just use Mozilla.

    2. Re:HCI anyone?? by douthat · · Score: 3, Insightful

      I don't see other popular media players using the standard windows UI. Do you?

      The above is a moot point, anyway. Keeping the UI of an application consistent with the UI of all the other apps on a particular OS is very important if you want to increase the rate of adoption. Media players are an exception because just about every media player fux up the UI to a confusing level.

      Take the look and feel of another popular open source media player as an example. When my mac buddies look for a video player capable of playing mpeg-2 (or whatever file-type it is they're having problems with that day) if I point them to VLC, they love it! It looks and feels exactly like any other mac application they use, from the metal UI, to the menu at the top of the screen, to the double-clickable .app bundle and high-res icon. They end up accepting it alot more easily than an application that didn't fit the Mac look and feel. Similarly, when you run VLC in Windows, it LOOKS and FEELS like a windows app, and on linux, it LOOKS and FEELS like a linux app. Hell, on BeOS, it looks and feels like a beos app.

      I think it would be a step backwards for FireFox to consolidate on a single theme across all platforms.

      --
      She loves me: 09F911029D74E35BD84156C5635688C0 She loves me not: 09F911029D74E35BD84156C5635688BF ...
  19. Re:great by linuxci · · Score: 2, Informative

    You can do so in Firefox but they're implemented differently in Firefox than the suite.

    If you click on a link to add a sidebar panel then it'll ask you where you want to file a bookmark, then to open the sidebar you can look in the appropriate place in bookmarks.

    This bookmark approach also means you can turn any bits of HTML into a sidebar panel. Just bookmark a page, go to properties and check "Open this bookmark in the sidebar"

  20. To: Mozilla Devs by Anonymous Coward · · Score: 2, Insightful

    Please don't end up like the XFree86 developers, and completely ruin your project. Listen to the users, just give it a try. Now that wasn't that hard now was it?

    I love Firefox, without doubt the best browser yet, and it isn't even 1.0. Keep it fast and light, bloat is what made regular Mozilla suck, face it.

  21. From my reading of it by Chuck+Chunder · · Score: 4, Insightful

    The Mozilla devs did the right thing and asked about having Qute freely licenced 6 months ago. They were apparently told no and have therefore taken the only reasonable course left to them, sourcing another theme.

    The new theme might not be brilliant but it is a work in progress and rather importantly is freely licenced so other people will be able to tweak it over time.

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
    1. Re:From my reading of it by Chreo · · Score: 2, Interesting
      The Mozilla devs did the right thing and asked about having Qute freely licenced 6 months ago.
      From my reading of Ben's post in response he wrote that Arvid "INDICATED" (according to Ben) that he was not ok about having others create derivative works using stuff from the Qute theme.

      Now, to me, an important product as Mozilla require a "final answer" from Arvid on such an issue i.e. "The license on Qute have to be changed or we need to replace Qute with another theme. Will you change the license?". A final "no" then, would entitle the Moz devs to change default theme. It seems unfair both to Arvid and the creators of the new theme to not having cleared this issue before.
      --

      Life is what happened when Good Intentions met Harsh Reality (the brother of the more infamous Chaos).
  22. Caution 0.9 will break ALL your extensions by Anonymous Coward · · Score: 3, Informative


    do not install 0.9 until (if) the extensions have been updated as it will break

    once again backwards compatibility has been sacrificed (and we are not even at 1.0 yet) we had now 200+ extensions have to be updated and some have been abandoned as they worked, now they will be broken and useless

    i hope all this aggro was worth it, or you might find a lot of people just give up with it and go back to IE while its got a lot of failings at least you know where you are with it and it doesn't keep breaking every month

    1. Re:Caution 0.9 will break ALL your extensions by colinramsay · · Score: 4, Informative

      0.9 will FIX the extension system in Firefox, which has been one of it's weakest points thus far. After 0.9 there will be no further major shifts in the way extensions are handled, and so this is the first and only time that extensions have been broken in this way.

      It's a necessary change.

    2. Re:Caution 0.9 will break ALL your extensions by Eil · · Score: 4, Insightful


      once again backwards compatibility has been sacrificed (and we are not even at 1.0 yet)

      Uh, hello? How did this get modded up?

      Rather than feeding this relatively obvious troll, I'll simply remind folks that the whole POINT of the pre-1.0 development cycle is to break things. And nobody's forcing anyone else to use Firefox, stable or not. End of story.

  23. Slashdot Rendering by md81544 · · Score: 2, Interesting

    Apologies for only just vaguely being on-topic - but does anyone know what the progress is on the Slashdot rendering problem under Firefox (it gets mentioned regularly when Firefox comes up as a topic). I would have thought it would be an important fix for the Slash guys to put in, as I regularly have to refresh a page three or four times before I get any text in the main boxes. This can't help bandwidth...

    1. Re:Slashdot Rendering by marq00z · · Score: 3, Informative

      This bug has been fixed recently. (bug 217527).

  24. You act like IE is stable... by gtaluvit · · Score: 4, Insightful

    I've seen IE barf on pages before. No browser is going to be perfect and I think explaining to people that you may have to close and restart a browser during the day (if they keep it open THAT long) is a lot easier than saying "ok, if you close those 5 pop ups and uninstall CometCursor, you'd see the page you're lookin for."

    --
    - gtaluvit (prnc. GOT-tuh-LUV-it)
    1. Re:You act like IE is stable... by cgenman · · Score: 2, Interesting

      Parent has a very good point. IE still freaks out with regular use, bloating up to tremendous size and crashing. Opera (which I'm writing this on now) also crashes, perhaps once a day. It's not such a big deal in Opera, because it saves what pages you're looking at, but it still happens. Mozilla crashes. iCab crashes. I can't vouch for Konqueror or Safari, as I haven't spent enough time with either.

      In short, while bugs are annoying, FireFox isn't buggier than any of the other browsers out there, and in some comparisons is a lot less buggy. Compared to Opera's break-fix development cycle, FireFox is a rock of gibraltar.

    2. Re:You act like IE is stable... by Kyouryuu · · Score: 4, Insightful
      Just because IE isn't stable doesn't mean Firefox can't aspire to be. IE is an archaic browser as far as I'm concerned, and that's why Mozilla and Netscape are actually gaining momentum. Prior to Mozilla 1.0, IE dominated. Now, at least according to my statistic, it's more of a 90%-10% or 85%-15% distribution. And although that may seem small, in something as gigantic as the browser market, that's actually quite a lot of people.

      Why are they gaining? They offer technologies people want. Tabbed browsing, pop-up blocking, and are generally less crashy. They are also generally more immune to the various sorts of crap unscrupulous advertisers have been pulling that "infects" IE. To keep gaining, these browsers need to keep doing this. That means not allowing large and highly documented bugs like the memory leak in question to be ignored.

    3. Re:You act like IE is stable... by farnsworth · · Score: 2, Informative
      It's not such a big deal in Opera, because it saves what pages you're looking at

      If I understand you correctly, there is a way to do this in mozilla as well. Set the pref browser.startup.page to the integer '2', and mozilla/firefox/et al will start up on the page last loaded.

      --

      There aint no pancake so thin it doesn't have two sides.

  25. Re:ow, new design :D by Ruediger · · Score: 2, Informative

    according to the firefox roadmap it should be out this month.

    --
    "...personality goes a long way."
  26. Plastikfox by twener · · Score: 2, Interesting

    I don't care about the default look as long there is Plastik for Firefox available which also includes Crystal icons and Cancel<->OK button swap.

  27. It is fixed... by WD · · Score: 2, Informative

    Assuming you're talking about this bug:
    http://bugzilla.mozilla.org/show_bug.cgi?id= 205893

  28. Re:GTK 2 by damiam · · Score: 2, Interesting
    Firefox isn't well-threaded on any platform (I'm using it under Windows on a dual Athlon and it hangs when I load a complex page into one tab). QT wouldn't change that.

    I'd be intrigued to hear why you believe GTK is so "fundamentally backwards", seeing as just about every useful Linux app (except for maybe KDevelop, K3B, and OO.o) is written in it.

    --
    It's hard to be religious when certain people are never incinerated by bolts of lightning.
  29. here's a link to the theme itself by reeb · · Score: 2, Informative


    It looks very nice!! (a work in progress, and this maybe an older version).

    save to disk: pinstripe theme

    use the tool here to install it.

  30. Idiots love skins by Tom · · Score: 4, Interesting

    Actually, the look of things is about the only thing that even total idiots do change about their computers.

    Many, many thousands of machines out there run without having ever been update since install, with every service under the sun enabled, and probably with the default passwords still in place. However, these same machines have custom backgrounds, colour cursors, sound effects and a dozen screensavers.

    Skins are big with people who don't know how to change the Start menu and believe Linux must be a windos program, because how can something run on a computer if it isn't a windos program?

    --
    Assorted stuff I do sometimes: Lemuria.org
  31. IE Theme? by callermann · · Score: 2, Funny

    Ok so who's gonna be the first person to write an IE look alike theme ;-)

  32. Re:How about we fix the more important things firs by Anonymous Coward · · Score: 2, Interesting
    4/10 troll, it works fine.
    <html>
    <head>
    <style type="text/css">

    h1 { display: block; }
    h2 { display: inline; }

    </style>
    </head>
    <body>
    <h1>Th is </h1>
    <h1>Is </h1>
    <h1>Block </h1>
    <h2>This </h2><h2>Is </h2><h2>Inline</h2>
    </body>
    </html>
  33. Grandparent is NOT a troll, proof! by Anonymous Coward · · Score: 2, Interesting

    Before calling someone a troll, please invest a little more time than basic examples.

    Proof:

    <html>
    <head>
    <style>
    #test, #test2
    {
    display: inline;
    width: 250px;
    padding: 0px;
    margin-top: 10px;
    margin-right: 10px;
    vertical-align: top;
    border: solid 1px #333333;
    }
    </style>
    </head>
    <body>
    <div id="test">
    <div class="a">aaa</div>
    <div class="b">bbb</div>
    <div class="c">ccc</div>
    <div class="a">aaa</div>
    <div class="b">bbb</div>
    <div class="c">ccc</div>
    </div>
    <div id="test2">
    <div class="a">aaa</div>
    <div class="b">bbb</div>
    <div class="c">ccc</div>
    <div class="a">aaa</div>
    <div class="b">bbb</div>
    <div class="c">ccc</div>
    </div>
    </body>
    </html>

    1. Re:Grandparent is NOT a troll, proof! by colinramsay · · Score: 2, Insightful

      Please. This just shows your lack of understanding of the entire issue. The reason that your examples appear under each other is because display is not inherited. Therefore the divs inside test and test2 have a display:block - the breaks caused by such a block level element cause them to be displayed on a new line.

      Basic CSS, confused by the fact you have nested it in another div.

  34. I reported the leak on October 17, 2003: by Futurepower(R) · · Score: 3, Informative


    I reported the memory leak on October 17, 2003:

    Firefox 0.8: All instances crash. Memory leaks.
    http://bugzilla.mozilla.org/show_bug.cgi?id=222660

    (Copy and paste the link to view the bug report.)

    Please add your experiences to the report.

    I reported the same bug in Mozilla browser, a long time ago. Huge memory leaks have existed since Mozilla version 1.0.

    A recent experience: After two days of opening and closing instances of FireFox, with two FireFox instances open and maybe 5 tabs total, the FireFox memory usage in Windows XP was 374,656 kilobytes. When I closed one of the instances, the memory usage went UP to 385,868 kilobytes.

    When you reach the limit of installed memory, Windows XP has to do its terrible disk thrashing thing. If Bill Gates weren't so poor, he could fix that. The advantage of open source is that there is at least a chance that the FireFox bug will be fixed.

    1. Re:I reported the leak on October 17, 2003: by linzeal · · Score: 2, Funny

      Send me 512 megs of ram every 6 months to keep up with feature bloat?

    2. Re:I reported the leak on October 17, 2003: by Alexis+de+Torquemada · · Score: 3, Informative
      Blatant MS bashing gets you mod points aparently. When you reach the upper limit of memory, this "disk thrashing" you speak of is the cache being resised. All that you need to do to stop that is set your cache minimum size the same as the maximum. No more disk thrashing. Or you could just hate on M$, that might be even easier.

      Poppycock. In order to shrink the cache, only dirty pages have to be flushed. However, dirty pages have to be written much earlier than that in order to reduce the damaging effects of system or power failures anyway, so most of the cache will very likely not be dirty at that time. Cache pages which are not dirty, i.e. identical to the version on disk do not need to be written out, but can simply be discarded. So shrinking the cache should typically involve little disk I/O. Exceptions would be times where you do write lots of data to harddisk (e.g. downloads over a fast connection).

      Btw, Linux may write "anonymous" pages (e.g. application memory) that haven't been recently accessed into swapspace before it actually runs out of physical RAM, but keeps them in RAM as "not dirty". That way, it can also just discard them once memory conditions get critical, and thus avoid a lot of disk I/O delays.

  35. Screenshot of the New Default Theme by sgarrity · · Score: 5, Informative
  36. Screenshot of the new theme by Anonymous Coward · · Score: 3, Informative

    The author of the new theme, Kevin Gerich, has posted a screenshot in his blog:
    http://kmgerich.com/archive/000062.html

  37. Re:The new theme by CeleronXL · · Score: 2, Informative

    And here is a complete screenshot of the new theme. I think this is a huge step backwards.

  38. Re:And what was Firefix was for, again ?? by Jugalator · · Score: 2, Informative
    --
    Beware: In C++, your friends can see your privates!
  39. Re:It's just Windows by E_elven · · Score: 2, Insightful

    It may be just me but when the 'lean', 'no-nonsense' and 'stripped' version of software requires 27MB to run with two open tags I think it's perfectly fine to blame the developers of that software, even if there were no extra resource leaks.

    I hope someone will write a browser that will parse only valid XHTML 1.1/CSS and nothing else. Would cut the executable in half not to try to support the horrible code people put on the web a few years ago.

    --
    Marxist evolution is just N generations away!
  40. SVG Support by kiyut · · Score: 5, Interesting

    How about firefox native SVG support? Does anyone know if native SVG is included by default install?

    --
    Sketsa
    SVG Graphics Editor
    http://www.kiyut.com
    1. Re:SVG Support by marq00z · · Score: 2, Informative

      SVG support is in the CVS, but it's not considered stable at the moment. It won't make it into the 0.9 release of Firefox (it's not even a part of the "aviary" pre-0.9 branch).

      So, if you want to have an SVG-enabled Firefox you have to pull the trunk source from the CVS and then add these lines to your .mozconfig before building the browser (I assume you're using GNU/Linux):

      ac_add_options --enable-svg
      ac_add_options --enable-svg-renderer-libart
      export MOZ_INTERNAL_LIBART_LGPL=1
      mk_add_options MOZ_INTERNAL_LIBART_LGPL=1

      Some people from the MozillaZine "Firefox Builds" forum are creating their own builds. If you've got luck, you may find an SVG-enabled build there, too.

  41. FireFork? by gumpish · · Score: 2, Interesting

    Will this blunder by Goodger & Co. be the straw the broke the camel's back and cause a FireFox fork (FireFork?) to rise to prominence, a la the XFree86 story?

    We can only hope.

  42. Well he could... by rsilvergun · · Score: 3, Insightful

    write his OS so that applications that aren't in use get put out to swap and stay there. I'll admit I don't really understand the technical aspects here, but the complaint seems to be that the this is 'thrashing'; which usually means _sustained_ memory swapping for no really good reason. I've had plenty of instances of that in WinXP, and a lot less of it in Linux (and I've heard great things about the BSD's but I'm too lazy to install them right now). Anyway you cut it though, I think we'll all agree the memory management in WinXP (and probably every other OS on the planet to be fair) could use some work. The grandparant is just ticked off that with all the money XP costs, something as basic as memory management isn't a top priority.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Well he could... by Kyouryuu · · Score: 2, Interesting
      Perhaps, but even then you have to hit a fundamental limit. Even if you swap out applications to compensate for the rising demand, at some point that demand is going to outpace the available RAM. Then what? Linux is not immune to this either, though perhaps it handles it more gracefully. Windows XP goes into a very sluggish, stuttering mode where it becomes difficult to innoculate the offending program.

      But on a more basic level, while Microsoft can work to prevent thrashing, program authors also need to fix legitimate memory leakages. Otherwise, it's like asking the government to step in to regulate something because people are too lazy to fix their own problems (i.e. video game violence, movie violence, fast food lawsuits, etc). It's really not Microsoft's responsibility to "Make Firefox not leak memory." Microsoft's job is to handle the "thrashing" gracefully if and when it does happen.

  43. Re:The new theme by chunkwhite86 · · Score: 4, Insightful

    And here is a complete screenshot of the new theme. I think this is a huge step backwards.

    Remember that to gain market share, you have to design the product for the average idiot. Yes, you know the one; the guy that thought his CDROM was a cup holder.

    To win the average idiot, you need simple layout, bright colors, and hand-holding wizards.

    --
    I'd rather be a conservative nutjob than a liberal with no nuts and no job.
  44. Re:How about we fix the more important things firs by colinramsay · · Score: 4, Funny

    I have no idea what you're talking about with regard to Firefox CSS rendering, but it's fairly clear you have little idea how the box model works.

    display:block and display:inline have nothing to do with how elements are aligned. They control the behavior of an element within the document flow. An inline element, such as an anchor, does not disrupt the flow. A block level element has breaks before and after; as such, it will interrupt the flow.

    Your perceived alignment comes fromt this. When three inline elements follow each other, the act line words in a sentence and flow one after the other. When three block level elements follow each other, the breaks before and after the element cause each block to appear under the preceeding one.

    Just a quick lesson. If I were you, I'd read up on CSS and prepare some testcases with a well written bug report before you talk about rendering issues. From your post you appear to be fairly ignorant of what's really going on.

  45. I want a theme.... by fozzmeister · · Score: 2

    ... That looks like my OS (GNOME)! Firefox isn't too bad atm, infact its amazing that they have got as much looking like native, but its still not right, infact its still not anywhere close, my highlighting in the menu bar is a dull blue white text in sinks into the menubar. the items selected are rounded dull blue with white letters in firefox they are square edged. Sure its mostly there, but its not quite, and in UI issues not quite is not a great deal better than nowhere near! That's why i use Epiphany as my browser, but I use Firefox for developing (it really doesn't matter for that coz i use jEdit which is Metal Themed so that is nowhere near either)

  46. Re:It's just Windows by Kyouryuu · · Score: 2, Interesting
    It would also probably cut the number of web pages you can view by half as well.

    I still write in HTML 4.0 Transitional and validate it. Why should I be left out? XHTML is unnecessarily complex for my needs. At the end of the day, I merely want a site that looks reasonably good and is functional. I don't really need the wizardry and features XHTML can offer.

  47. Re:The new theme by ratsnapple+tea · · Score: 2, Interesting

    Wrong, wrong, wrong.

    This is why Linux will never gain significant market share on the desktop--it's being dumbed down in all the wrong ways, due to arrogant notions like these from smug Slashdotters who insist on looking down on average users. You know the kind. Average users like the doctor who performed a coronary bypass on you last year. Average users like the Pulitzer-winning journalist who wonders why she has to endure a ten-step wizard just to save a document. Is it because she's stupid? Or is it because some acne-faced programmer thought she would be stupid?

  48. For those curious, here's a Pinstripe gallery by Overly+Critical+Guy · · Score: 2, Informative

    Here's what Pinstripe looks like. Goes to show OS X still has the most beautiful, pleasant, and clean-looking GUI around; no wonder everyone tries to rip it off yet fails:

    Pinstripe Firefox Gallery

    --
    "Sufferin' succotash."
  49. No... by Overly+Critical+Guy · · Score: 2, Insightful

    To win the average idiot, you need simple layout, bright colors, and hand-holding wizards.

    To win the average idiot, you need to do two things:

    1.) Make something fun to use. That encompasses everything from a pleasant visual look to a simple yet powerful interface. Something most OSS lacks.

    2.) Don't call them "idiots." They're not idiots just because they have enough of a life to not treat browser and operating system wars like religious crusades, like we do.

    --
    "Sufferin' succotash."
  50. IE style favorites by Tekoneiric · · Score: 2, Interesting

    I just they'd enable a user to select IE style favorite handling (in .lnk files) if a user wanted it. I prefer the way IE handles favorites.

    --
    *It's not what you can do for the Dark Side but what the Dark Side can do for you!*
  51. Something is wrong with MS memory management... by Futurepower(R) · · Score: 2, Interesting


    Except that when you reach the memory limit in Windows XP, the OS often becomes unstable, and remains unstable until you reboot.

    Something is wrong with MS memory management, but I have never been able to determine what makes it go bonkers.

    You say, "All that you need to do...". That's a good nickname for Windows XP. It's an "All that you need to do..." operating system. Go a little bit deep into how it works, and you begin experiencing its sloppiness.

  52. Re:It's just Windows by E_elven · · Score: 2, Informative

    XHTML is a misleading name. Essentially all XHTML is is simply an XML document type -it has a schema, and, yes, it is theoretically extensible just like any XML document. The extensions are known as releases -XHTML 1.0 vs. XHTML 1.1, which have different schemas.

    The individual web developer will not extend XHTML in any fashion (he can, but then it's not of the same document type anymore and will therefore not work with the clients (browsers)).

    XHTML is mostly a subset of HTML (although one or two new tags are defined also). See here for all XHTML 1.1 tags.

    The reason for XHTML's existence is that HTML concentrates (heavily) on presentation as well as structure, and it was felt that this should not be. So XHTML defines the structure of a given document and leaves any presentation of that data to some other entity (like any good XML document)*. The presentation layer is called CSS or Cascading Style Sheets.

    * I don't mean that an XML document can't define presentation per se -what I mean is that a good XML document does one thing and one thing only: presents some data in a structured manner (for example, this post contains a MemberName, Subject, Text, ModerationScore and so on). There's nothing that prevents using XML to describe presentation, but it should not be presentation -that's a very important distinction. So theoretically an XHTML file describing the structure of the document could be accompanied by another XML file that described how it was to be presented, but at least for now that task has been given to CSS. For information about XML as presentation description, you can take a look at XUL from Mozilla.

    --
    Marxist evolution is just N generations away!