Slashdot Mirror


Mozilla 1.2 Betas Start Flowing

Asa Dotzler writes "Today mozilla.org released Mozilla 1.2alpha. This is a preview of what's to come with Mozilla 1.2 expected in early November. The new alpha contains great new features like Type Ahead Find which allows quick web page navigation when you type a succession of characters in the browser. In addition to the new features Mozilla 1.2a contains stability and perfomance improvements including a major boost in the speed of downloading mail on Mac OS X.This release comes on the heels of the security and bugfix follow-up to Mozilla 1.0. If you're a 1.0 user and you're not upgrading to Mozilla 1.1 or newer then you are strongly encouraged to get Mozilla 1.0.1 for security and stability fixes."

7 of 367 comments (clear)

  1. Re:Well at this rate... by evilquaker · · Score: 4, Insightful
    Mozilla will become feature complete when compared to IE6 sometime in the beginning of next year :-)

    Really? IE6 has mouse gestures, tabbed browsing and pop-up blocking?

    Sounds to me like Mozilla is already more feature complete than IE... little conveniences like type-ahead find really don't compare to the three I mentioned above...

    --
    To within half a percent, pi seconds is a nanocentury. -- Tom Duff
  2. Re:Umm.. Just a question... by psykocrime · · Score: 4, Insightful

    What can the new mozilla do that I can't already do in Opera or IE?!?!?

    That you can't do in Opera? Don't know, I don't use Opera.

    That you can't do in IE:

    1. Tabbed Browsing

    2. Use mouse gestures

    3. use radial context menus

    4. use type ahead search (ala Emacs)

    5. Use Mycroft search plugins to search from the URL bar or Sidebar.

    6. Use other neat Sidebar plug-ins

    7. use custom themes to "skin" the browser.

    8. chat on IRC

    I'm sure there are other things as well, but those are the first ones that come to mind.

    --
    // TODO: Insert Cool Sig
  3. Re:Well at this rate... by mshiltonj · · Score: 3, Insightful

    You misunderstand: what Mozilla allows you to do is block *unrequested* pop-up windows. Other, requested pop-ups work just fine.

    Mozilla *thinks* the popups are unrequested, but, as part of the application, the behavour is desired.

    At times, the onLoad event of the document object opens one or more new windows as part of the application.

    Among other things, this is what the pop-up blocker blocks. 99.9% of the time, this is exactly what I want. But for this particular application, I really *do* want (need) one or more new windows to be opened on a document onLoad event.

    I have not found a way to enable or disable Mozilla's behavior in this regard on a per-site basis.

    After make the earlier post, I realized that what I need, for pop-up blocking, is the same as already offered with cookie and image management.

    Mozilla lets me block or allow cookies and images on a per-site basis. I'd like the same level of granularity for pop-up blocking.

    Is this possible? Does anyone else have this need?

  4. Re:Well at this rate... by Sj0 · · Score: 3, Insightful

    use the quickloader. IE has it's stuff loaded already, why not level the playing field?

    --
    It's been a long time.
  5. Re:Opening new windows by sjbe · · Score: 3, Insightful

    I've been slightly annoyed by this behavior, though you can work around it pretty easily. Mozilla to the last tab you were in so I just usually open a new tab (hit Ctrl-T) and then do the link. An annoying extra step I'll concur but I think if that is the only thing holding you back work around it. Mozilla has too much OSS goodness to let something so small ruin it for you. :-)

  6. Re:Usability bugs by bunratty · · Score: 3, Insightful
    I'm always surprised that yet another Mozilla version does not fix big usability bugs.
    If you give us the bug numbers, we can vote for them or even nominate them to be fixed in an upcoming version. Throw us a friggin' bone here, people!
    --
    What a fool believes, he sees, no wise man has the power to reason away.
  7. Re:Well at this rate... by MatriXOracle · · Score: 5, Insightful

    Maybe if you read your own link (bugzilla bug 28568, copy link and paste in address bar) you would notice that this is fixed in 1.2a, but you have to use a hidden pref to enable it:

    user_pref("browser.xul.error_pages.enabled", true)

    So next time, try READING instead of posting a useless flame about your favorite bug.