• On BNET: Why Domino's admitted its pizza sucked
advertisement
July 14, 2006 8:20 AM PDT

Firefox 2.0b1 (#2): Minor issues, improvements

by CNET staff

As we reported yesterday, the most prominent issues with Firefox 2.0b1 concern already-installed extensions and themes, of which many are disabled post-update. Most of the broken extensions/themes will require updates for compatibility with the new release.

Users are noting a few other issues, with plug-ins and specific site accessibility.

MacFixIt reader Hank writes:

"With Firefox 2.Ob1 I can no longer view video news clips from the CNN home page. I have Flip4Mac installed in my Mac OS X 10.4.7 system."

Jerry Davis reports issues accessing specific sites:

"I was using Firefox 1.5.0.4 because it successfully coped with my four banking sites. Version 2.0b1 does not. I went back to my previous version without exploring the new release any further."

Meanwhile, MacFixIt reader Justen laments the lack of separate home page and new window settings in Firefox 2.0b1.

Justen writes:

"The other browsers I use regularly (Camino and Safari) allow you to set a destination home page (e.g. www.macfixit.com), but also allow you to have a new page open blank.  I see no way to do this in Firefox; if you set a home page to a website, it forces you to open that page with every new page.  If you want a blank page, you have to set your home page to blank."

Finally, a poster to VersionTracker's feedback system reports on enhanced stability with the sites he frequents in this Firefox release.

"I've been using Firefox for a long time, now, but have had stability issues on my TiBook/550 running 10.3.9. So far, the 2.0b seems more stable than 1.5.x.x on my machine. In addition, the rendering engine appears to be much faster and more accurate, even with the new built-in features, some of which replace extensions I had installed. Now, most of my extensions/toolbars/themes are disabled, which is a nuisance, but if I couldn't use 1.5 for long with them, anyway, no harm done. So, so far I give the 2.0b a thumbs up."

Feedback? Late-breakers@macfixit.com.

Previous coverage:

Resources

  • poster
  • Late-breakers@macfixit.com
  • Firefox 2.0b1 released: Pr...
  • More from Late-Breakers
  • Recent posts from MacFixIt
    iTunes 10 user interface sees some minor changes
    Apple seeds iOS 4.1 Gold Master to developers
    Possible fix for Harman Kardon iSub problems with PowerPC Macs
    Precautions to take before installing iTunes 10
    A reminder on how to reset your Mac's system password
    Mail messages appearing blank
    Adobe Lightroom update brings direct Facebook publishing; Camera Raw 6.2 released
    Weekly troubleshooting utilities update
    Add a Comment (Log in or register) (4 Comments)
    • prev
    • next
    by Lou Zer July 14, 2006 9:41 AM PDT
    For better tab management (on the 1.5 browser), I use Tabbrowser Extensions, found at http://piro.sakura.ne.jp/. It offers a ton of features just dealing with tabs, including re-opening, refreshing all tabs, groups, etc.

    And not to just be irritating, but I thought the point of firefox was to make a small browser that was extensible to add features people would want. Aren't we heading down the same road as navigator by pushing in more and more features directly?
    Reply to this comment
    by morbius July 14, 2006 11:34 AM PDT
    "Meanwhile, MacFixIt reader Justen laments the lack of separate home page and
    new window settings in Firefox 2.0b1."

    This seems to be the case with 1.5.0.4 as well.
    Reply to this comment
    by cartoonasaur_dotmac July 14, 2006 11:34 AM PDT
    <class="merchant"><span>&#62;</span><div class="datestamp"><i>This is a reply to a previous comment by morbius</i></div></class><br />
    DON'T make a new WINDOW.
    Make a new TAB. Blank blankitty blank, Baby!
    Reply to this comment
    by Swift2 July 17, 2006 9:04 AM PDT
    I don't have any problem playing CNN video (in Pipeline) using Firefox 2.0b1,
    with Flip4Mac. Though, I do have the Universal beta 2.10b4 version installed.
    Reply to this comment
    (4 Comments)
    • prev
    • next