Slashdot Mirror


Firefox Roadmap Update

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

6 of 43 comments (clear)

  1. What's new in 1.1/2.0? by MBCook · · Score: 2, Insightful
    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.

    --
    Comment forecast: Bits of genius surrounded by a sea of mediocrity.
  2. Limit Scope of Session Cookies - 117222 by JPyObjC+Dude · · Score: 2, Insightful

    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

    1. Re:Limit Scope of Session Cookies - 117222 by QuantumG · · Score: 2, Insightful
      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 example, say you run bugzilla and phpmail on the same web site (assume also these both use session cookies, they probably don't). For bugzilla use the session variables bugzilla-login and bugzilla-password. For phpmail use the session variables phpmail-login and phpmail-password. Now configure both apps so they check for a session cookie on the login page instead of just assuming that a new login implies a new session.

      The browser is doing the right thing, the webapp developers just arn't playing nice together. Fixing the browser to fix these webapps is just plain bad mojo. In the mean time, if you want a work around, use different profiles.

      Oh, and the "security concern" about needing to close all FireFox windows to successfully log out of a webapp. That's such a load. You clear the session cookie in one window (say by the user pressing "logout") and it is cleared in all windows. If this feature were implemented this wouldn't be the case - less security, not more.

      --
      How we know is more important than what we know.
  3. "Preview Release/Developer Preview" by DarthMAD · · Score: 5, Insightful

    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.

  4. Re:Slashdot & Firefox by at2000 · · Score: 2, Insightful

    Yes

  5. Re:Slashdot & Firefox by Anonymous Coward · · Score: 1, Insightful

    Copy link location and then paste it people. Bugzilla won't allow links from Slashdot.

    https://bugzilla.mozilla.org/show_bug.cgi?id=217 52 7#c145