Mozilla Firefox 6.0 - Final


Recommended Posts

Mozilla Firefox 6.0 - Final

Firefox 6 - faster, more secure, easier to use and sporting a new look, this latest Firefox release sets a new standard for web browser innovation. Firefox is small, fast and easy to use, and offers many advantages over other web browsers, such as the tabbed browsing and the ability to block pop-up windows. View Web pages way faster, using less of your computer?s memory. Take Firefox with you wherever you go. Synchronize your browsing across multiple devices. Forget clunky URLs ? find the sites you love in seconds. Firefox has the most ways to customize your online experience specifically for the way you use the web. It is built with you in mind, so it?s easy and instinctive to use even the first time you try it. Thousands of Add-ons (little extras that augment Firefox to meet your unique needs) just waiting out there to help you do more, have more fun and be more creative online. Firefox keeps your personal info personal and your online interests away from the bad guys. Simply put, your security is our top priority.

Downloads:

Download Firefox 6.0 for Windows EN US File version: 6.0.0.4240

Other languages

All systems

aboutfirefox60.png

01:20.49 2011-08-13 Firefox Setup

33f6dc8bf51178af43a58c405c0a5c10 *Firefox Setup 6.0.exe

08:42.44 2011-08-16 Firefox Setup

33f6dc8bf51178af43a58c405c0a5c10 *Firefox Setup 6.0.exe

Link to comment
https://www.neowin.net/forum/topic/1018398-mozilla-firefox-60-final/
Share on other sites

thanks for the update but i am waiting for Firefox 7 to be final as ill stick with Aurora channel for now as Firefox 7's memory usage is hugely improved which means prior versions are obsolete/not worth using.

i been using Firefox 7 for over a month now and i won't go back to to big memory improvements over prior versions.

Ha - if it wasn't for Google's lame versioning strategy, FF 6 would - and should - have been 4.2. :rolleyes:

Ha - if it wasn't for Google's lame versioning strategy, FF 6 would - and should - have been 4.2. :rolleyes:

i agree as it's been ages like that up until recently. because full version number changes used to mean fairly big leaps. now you just get small differences between FF4 to FF6. FF7 is where the big leap is at anyways due to the very noticeable ram use reduction.

because with the usual version numbering it would have basically been like this...

Firefox 4

Firefox 4.1 (i.e. Firefox 5)

Firefox 4.2 (i.e. Firefox 6)

Firefox 5 (i.e. Firefox 7 (since the very noticeable ram reduction would be a major boost to the browser))

Ha - if it wasn't for Google's lame versioning strategy, FF 6 would - and should - have been 4.2. :rolleyes:

I'm going to sleep now. Wake me up when people stop complaining about this and just be happy that they are actually releasing updates faster.

I must have totally missed FireFox 5 haha, I was sure the latest was version 4.

Ha - if it wasn't for Google's lame versioning strategy, FF 6 would - and should - have been 4.2. :rolleyes:

Google don't make any deal what so ever about what version the browser is, so it shouldn't matter.

firefox 6 is a nice improvement, mainly in HTML5 capabilities, the other changes are rather minor. Not long until Firefox 7 beta, need the ram improvements badly, i hate firefox increasing in ram over several hours, supposedly firefox 7 will pretty much fix this.

Fx7 will enter Beta on 16th, so only a few more days of waiting.

Must this happen every time?

It's not really final until it's actually announced as a release. Then all the pages are up to date, and the build will have been fully tested and approved. So, use at your own risk, but why do we have to have a thread jumping the gun every time?

And, they're doing time-based releases, hence the version increment each time (because 4.1, 4.2, 4.3 forever would be silly). Just ignore the bloody version number.

I'm going to sleep now. Wake me up when people stop complaining about this and just be happy that they are actually releasing updates faster.

True. Yeah, this new versioning, like Chrome's versioning, is a bit misleading and artificial, but I'm glad they are rolling out improvements much more quickly instead of getting bogged down. Getting to 4.0 took way too long.

More than likely trying to keep up with rival browsers versions.

IE9

Opera 11

Chrome 13

FF4... Sounds pretty far behind the rest

Chrome doesn't advertise its version number anywhere. Chrome isn't trying to beat anyone's version number, and no one is trying to catch up to chrome's. Firefox isn't adopting a chrome style release cycle because of a damn version number, they are doing it for faster, consistent releases that get improvements to the end user faster, rather than the previous monolithic releases that let the current version get stale and behind (*cough firefox 3.6 cough*).

Chrome doesn't advertise its version number anywhere. Chrome isn't trying to beat anyone's version number, and no one is trying to catch up to chrome's. Firefox isn't adopting a chrome style release cycle because of a ****ing version number, they are doing it for faster, consistent releases that get improvements to the end user faster, rather than the previous monolithic releases that let the current version get stale and behind (*cough firefox 3.6 cough*).

Capture.PNG

Unless you mean on their download page, then no they don't - but chill... no need for swearing about a browser !

EDIT - actually

Capture.PNG

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'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • 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
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!