Firefox 3.0 Beta 1


Recommended Posts

apparently there are still 700 bugs ish that havent been fixed and 120 ish may still be left in 3.0 final:( they should just push the release date back, i dont wanna have to have for 3.02 to get a stable firefox3. im gunna hold off until rc3 or later to give it a whirl.

they already started. that's why it looks crap. cause they started. but haven't yet finished ;)

the toolbar is now unified. but it still doesn't paint in the proper shade of gray. the preferences dialog still doens't have the unified toolbar and the sizing is broken.

places seems like a nice thing, though :)

So far, the only differences from 2.0 that I've seen are, it zooms the entire page instead of just the text. Under Tools, Add-ons, Plugins are now listed, which you can disable. Under Tools, Options... Applications, I think I see more apps listed. Otherwise it looks more like a version 2.1 than 3.0... Of course, there may be major changes under the hood.

Oh, yes, and I forgot about the cooler FTP browser...

Edited by Gus.
So far, the only differences from 2.0 that I've seen are, it zooms the entire page instead of just the text. Under Tools, Add-ons, Plugins are now listed, which you can disable. Under Tools, Options... Applications, I think I see more apps listed. Otherwise it looks more like a version 2.1 than 3.0... Of course, there may be major changes under the hood.

Who decided that was a good idea? Did Microsoft or Mozilla even ask anyone who used the text zoom feature if that was better? If the text gets up to a size that's readable to me, I have to scroll sideways to read everything (yes, my eyes suck).

Wasn't Firefox 3 the major new / uber leet version of Firefox? I don't see anything much new and what is new hardly amounts to a whole version number change.

It's a new version of Gecko, there's Places, and the new style is coming. It is, despite what it seems at the beta stage, a big update.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!