Please create an account to participate in the Slashdot moderation system

 


Forgot your password?
Close
typodupeerror
×
Mozilla The Internet

Firefox Roadmap Update 43

Posted by timothy from the turn-left-go-fast dept.
wikinerd writes "The Firefox roadmap has been updated by Ben Goodger, Firefox lead engineer, who recently moved to Google. The updated roadmap reveals that Firefox 1.1, codenamed "Deer Park", will be released in June, after an Alpha release in March and a Beta version in April. Firefox 1.5 ("The Ocho") and 2.0 will be released later in the second half of 2005."
This discussion has been archived. No new comments can be posted.

Firefox Roadmap Update More

Firefox Roadmap Update

Comments Filter:

  • What's new in 1.1/2.0? (Score:3, Insightful)

    by MBCook ( 132727 ) <foobarsoft@foobarsoft.com> on Monday January 31, 2005 @08:48PM (#11535798) Homepage
    After a few minutes looking over the links, I didn't see a list of what the changes would be for 1.1 or 2.0. So for my education (and to prevent 30 comments with this same question)... can someone point us to that info?

    Thanks.

  • Roaming profiles for Firefox (Score:5, Interesting)

    by Matt Perry ( 793115 ) <perry,matt54&yahoo,com> on Monday January 31, 2005 @09:04PM (#11535913)
    Any hackers want to take on bug 249343 to port the Mozilla roaming profile code to Firefox?
    • I still would like to see bug #67127 "Newline in tooltips (title attribute) converted to black bars" fixed... this bug dates back almost 4 years now!
      • But just so everyone knows where you're coming from. You don't want this fixed enough to fix it yourself (learning how to program if necessary) or to pay someone else to fix it for you.

        Obviously if a bug is 4 years old it is not very important. If it is important to you, do something about it (and no, complaining that people who are already giving you a free lunch are not putting your favourite desert on the buffet is not "doing something").

  • Limit Scope of Session Cookies - 117222 (Score:3, Insightful)

    by JPyObjC Dude ( 772176 ) on Monday January 31, 2005 @09:18PM (#11536009)
    The biggest bug I see in *zilla is definitely the session cookie handling:

    https://bugzilla.mozilla.org/show_bug.cgi?id=117 22 2

    IE (unfortunately) does a very good job at handling session cookies where: Any window launched from a browser window (window.open(), file>new>window, ctrl-N, ctrl-T open link in new window...) should share the same session cookie. Any new Browser window launched from the Operating System level icon or menu should have it's own session cookie.

    Unfortunately, this bug has not been picked up by anybody and is not on the roadmap for any release.

    As you can read from the threads, some users have serious problem with this bug as it does impact some multi-user security issues.

    The scope of fixing this is probably very huge and impacts many subsets of the mozilla frameworks. But is it not possible to do this just for Firefox? Maybe it being a `Browser Only` could allow hackers to branch some code designs in such a way that they can get a simplified model working and write it in a way that can be merged to the moz trunk without too much pain.

    Personally, this one is just way too huge for a minor hacker like I to tackle but I'm sure there are some brave souls willing to tackle this Everest of an issue.

    JsD
    • Yawn, this is a feature request, not a bug. If it is so important to you pay someone to code it. Here's an idea: why not get together all the people you can find who want this feature and pool your funds?

      That's the way open source works: the person with the itch does the work, be it by firing up their source code editor or by paying someone else to do it for them.

      • THIS IS NOT A FEATURE request it is a hinderance to the compatibility of firefox with many websites, and therefor a bug.
        • Blah. It's a matter of opinion.

          Feature Request: Multiple logins on the same web site (that use session cookies).

          Bug: FireFox makes user log into unnecessarily when using multiple logins on the same web site (that use session cookies).

          Frankly I think it's a bug with the whole concept of session cookies. If you're a web developer and you want to fix this for your users it's really simple, use a session variable for username/password that is different for every app that you run on your website.

          For exampl

          • Frankly I think it's a bug with the whole concept of session cookies. If you're a web developer and you want to fix this for your users it's really simple, use a session variable for username/password that is different for every app that you run on your website.

            Doesn't always work. Take, for example, the users who might want to use the SAME app with two different logins at the same time. Happens at my work all the time - one of the main reasons why people here use IE. I use Firefox because I don't have t
            • This still isn't a bug. If it's a supported and desirable feature of the web application, then they need to support it themselves. Otherwise it's a perfectly legitimate and standards-compliant way of handling per-session cookies - and Firefoxes way of handling it is potentially much more secure when it involves things like banking. I can see a case being made for wanting the other behavior, but it's a feature request/behavior change that could(should?) be decided on by voting, not a bug that needs to be add
            • With FireFox you can just use multiple profiles if you really want that behaviour. So not only is this a feature request, it's a feature request that has already been implemented.. people are just bitching cause they don't understand why it is implemented that way and they think their suggestion to implement it a different way is acceptable because they've never looked at the code.
    • NO way. The java handling in firefox is mediocre at best. A java applet runs faster on IE still. Not to mention IE will run the applet, infect your PC and format your drive all at the same time.

  • "Preview Release/Developer Preview" (Score:5, Insightful)

    by DarthMAD ( 805372 ) <markhatesspam@@@gmail...com> on Monday January 31, 2005 @09:31PM (#11536093)
    I don't really buy their explanation about changing from the terms "alpha" and "beta" ... I think that most people using Firefox know what alphas and betas are and calling a beta a "preview release" seems to be almost misleading, creating a false sense of finality, which is what they are ostensibly trying to avoid. It's really just marketing, if you ask me- not that this is entirely bad, but perhaps could be better done. Whatever... that's my two cents.
    • I agree! Even the Windows users now know what a Beta is. There is no need to name it "Preview Release".

      Changing popular names confuse users. In general, when marketing people tinker with software they create a mess: Java 5 instead of 1.5, Preview Release instead of Beta, Windows 2000 instead of 5.0 (or Windows XP instead of 5.1 and Windows 2003 instead of 5.2), or even "Super Extra Fast Ultra DSL" (without any reference to the actual speed!).

      What the user wants is stable common names for various computing
    • No the majority of average windows users, average windows users are not known to be the most intelligent when it comes to their computers and internet.
  • The releases up to Firefox 1.0 [mozilla.org] were named after beaches.

    I believe "The Ocho" and "Deer Park" are rivers, but this is a complete guess. Ocho Rios is a resort town in Jamaca, Deer Park is a Gulfside town in Texas, so maybe the theme is still beaches...

    or maybe the theme is river deltas.

    • Re:Codenames... (Score:3, Informative)

      by GrumpySimon ( 707671 ) *
      One Tree Hill, Greenlane, Royal Oak and Three Kings aren't beaches. They're suburbs of Auckland, New Zealand [aucklandnz.com], where a certain Mr. Goodger comes from.

      (and me!)
      • And also there's the phrase, "Deer Park, that's good Browser" to be bandied about.
      • Ah, thanks for the clairifation.

        Releases 0.1 (Pescadero) to 0.5 (Naples) are all beaches or towns close to the ocean on the California Central coast.

        Indio and Glendale are down in the Los Angeles area, pretty far inland...

        Maybe I'm wrong about the whole beaches thing...
    • "The Ocho" was also the ESPN channel that the dodgeball competition was aired on, in the movie Dodgeball. That was the first thing I thought of at least. Funny movie...

      • "The Ocho" was also the ESPN channel that the dodgeball competition was aired on, in the movie Dodgeball. That was the first thing I thought of at least.

        You thought correctly [blakeross.com], then! Personally, though, I was disappointed that the Auckland suberb convention GrumpySimon mentioned ended: I was holding out for "Takapuna" where I was born, so I'd have some vague claim-to-fame...

  • Slashdot & Firefox (Score:3, Funny)

    by skinfitz ( 564041 ) on Tuesday February 01, 2005 @01:42AM (#11537685) Journal

    The updated roadmap reveals that Firefox 1.1, codenamed "Deer Park", will be released in June, after an Alpha release in March and a Beta version in April.

    ...but will it display Slashdot correctly?
  • When's 1.2 - "Ken Park" coming out?
  • What happened to release early and often?
    • They are, for a web browser. In the first place, there are preview/beta releases along the way, or for the brave, there are cvs builds. In addition, a web browser, as any developer or gentoo user will be happy to tell you, is a huge undertaking. If you consider that the release cycle of Internet Explorer typically corresponds to major Windows revisions, Firefox is doing about as well as can be expected. Finally, if you're impatient for new functionality or fixes, there's the excellent extensions community f

Slashdot Top Deals

We must believe that it is the darkest before the dawn of a beautiful new world. We will see it when we believe it. -- Saul Alinsky

Close