Recommended Posts

Firefox 3 Beta 4

Although it's in the "nightly" folder...it appears to be packaged up as a beta build. (Also I don't believe the .exe has been signed for Vista, but otherwise I would think the build is the same considering their beta 4 code freeze was 2/26? -- eagerly waiting beta 5 now)

Windows

http://ftp.mozilla.org/pub/mozilla.org/fir...7-firefox3.0b4/

Linux

http://ftp.mozilla.org/pub/mozilla.org/fir...8-firefox3.0b4/

Updated -- sorry wrong original linky :)

Edited by johnorien
Link to comment
https://www.neowin.net/forum/topic/623547-firefox-beta-4-win/
Share on other sites

For what it's worth: The build string of the latest nightly builds (to be found here) has been bumped up to 3.0b5 pre, and release candidates for 3.0 Beta 4 are available here.

I think beta 5 is going to end up being Firefox 3.0 RC 1soon-ish.

Edit: The XP theme was refined again. The site icon now matches the 'keyhole' design:

post-1302-1204642983_thumb.png

Edited by Mephistopheles

What I hate more on Firefox 3:

- On Firefox 2 when I hit Ctrl+T to open a new tab, the cursor focus automatically in the address bar, so I can start typing a web address immediately. On FF 3 this does not happen. So, I have to:

1) hit Ctrl+T

2) click with the mouse on the address

3) start typing

Maybe it sounds not to be a big issue, but it is something I do hundreds of times every day and I loose time.

- The auto-complete address by history just sucks. I type an address and I press Enter, but Firefox 3 does not open the address I typed. It opens the first selected address from the history. For instance:

Previously I had opened a site www.thesite.com/file.html

Later I go the the address bar and type www.thesite.com... but it does not open this. It automatically select www.thesite.com/file.html from the autocomplete drop down, so if I click Enter, it opens this.

- The "Go" button from the address bar has gone. I used it a lot on FF2 when I needed to reload a site without hitting Refresh (and waiting for ages for all the images to reload)

So, I will stay with FF2

Edited by ckgni
What I hate more on Firefox 3:

- On Firefox 2 when I hit Ctrl+T to open a new tab, the cursor focus automatically in the address bar, so I can start typing a web address immediately. On FF 3 this does not happen. So, I have to:

1) hit Ctrl+T

2) click with the mouse on the address

3) start typing

Maybe it sounds not to be a big issue, but it is something I do hundreds of times every day and I loose time.

- The auto-complete address by history just sucks. I type an address and I press Enter, but Firefox 3 does not open the address I typed. It opens the first selected address from the history. For instance:

Previously I had opened a site www.thesite.com/file.html

Later I go the the address bar and type www.thesite.com... but it does not open this. It automatically select www.thesite.com/file.html from the autocomplete drop down, so if I click Enter, it opens this.

- The "Go" button from the address bar has gone. I used it a lot on FF2 when I needed to reload a site without hitting Refresh (and waiting for ages for all the images to reload)

So, I will stay with FF2

I'm using the latest nightly and your Ctrl+T problems are no where to be found.

The same about the auto-complete issues.

What I hate more on Firefox 3:

- On Firefox 2 when I hit Ctrl+T to open a new tab, the cursor focus automatically in the address bar, so I can start typing a web address immediately. On FF 3 this does not happen. So, I have to:

1) hit Ctrl+T

2) click with the mouse on the address

3) start typing

Maybe it sounds not to be a big issue, but it is something I do hundreds of times every day and I loose time.

This is how it works in fx3 beta3 as well. I imagine this functionality will be restored, but that's the risk you run when using a minefield nightly build.
- The auto-complete address by history just sucks. I type an address and I press Enter, but Firefox 3 does not open the address I typed. It opens the first selected address from the history. For instance:

Previously I had opened a site www.thesite.com/file.html

Later I go the the address bar and type www.thesite.com... but it does not open this. It automatically select www.thesite.com/file.html from the autocomplete drop down, so if I click Enter, it opens this.

You are ether wong, or encountering another nightly-specific bug. If you are only pressing enter after typing something it should attempt to go to the URL you've typed, or do a google "I'm feeling lucky search" if it's not an actual URL, just like all versions of Fx have done.

As for the order of results, this gets better the more you use it. It scores your results based on how often you select something and how recently you've done so. So if you you frequently visit www.thesite.com then www.thesite.com/file.html will quickly move down in the results and www.thesite.com/ will reemerge on top. This is certainly an improvement in functionality over simple auto complete.

- The "Go" button from the address bar has gone. I used it a lot on FF2 when I needed to reload a site without hitting Refresh (and waiting for ages for all the images to reload)
The Go button appears when you are typing something into the URLbar.

Images have never reloaded by simply pressing the reload button, they've always loaded from the cache. You've always had to "super reload" by pressing Shift + Reload to reload everything from the web. This could again be a regression in this nightly build.

Edited by shakey_snake

<gripe>

That default theme for Windows is hideous. Why can't they just stick with simple, consistent icons like FF2? What's this keyhole crap...why did they waste their time with that?

People make custom skins/themes if they want a radical look to the browser. By default, KEEP IT SIMPLE, STUPID! Now you'll have to go download someone's FF2 theme for FF3 on each install. I guess that's a fair tradeoff IF they've fixed the performace issues. :rolleyes:

</gripe>

MY. GOD. The back and forward buttons are one of the ugliest thing I've ever seen in OS X... what's wrong with them!? It was okay in Beta 2 or 3.

91532877.png

I'm beginning to wonder whether any of the Mozilla developers use a Mac as their main computer. No application looks like that. As you said, the older versions of the skin, when they didn't have the keyhole design, were much, much better.

Using Hulu and Neowin, I'm at 121 MB and 93 MB Virtual

Another update: 3.05bpre is using RAM just like Firefox always does. Just 60MB on this site alone. Way to go Mozilla. /sarcasm

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

    • No registered users viewing this page.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!