Pale Moon is a custom-built and speed optimized Firefox browser. The project uses contributed Open Source code to create a full-featured, speed optimized browser based on the popular Firefox browser.
Having seen the advantages of other systems (e.g. Linux) with regards to programs being compiled specifically for the capabilities of the machine it is installed on, it became obviously clear that Windows users were at a disadvantage. Mozilla only releases windows executables with maximum compatibility in mind, meaning that Firefox is made to run on as many different systems as possible, sacrificing efficiency and speed in the process to be compatible with, by current standards, absolutely ancient hardware.
Mozilla does not provide optimized browser packages for Windows. That means you may be losing speed and efficiency when you use your browser.
That needs to change. Therefore Pale Moon project offers custom-built and optimized Firefox browsers for Windows Operating Systems. Make sure to get the most speed and efficiency out of your browser!
Pale Moon Main features
- Highly optimized for modern processors
- 100% Firefox sourced: As safe as the browser that has seen years of development.
- Support for Firefox extensions (add-ons), themes, and personas
- Able to use existing Firefox profiles, bookmarks, and settings with this migration tool
- Uses slightly less memory because of disabled redundant and optional code
- Significant speed increases for page drawing and script processing
- Support for HTML5 and WebGL (v4)
- Stability: experience fewer browser crashes.
- Support for SVG and Canvas, and downloadable fonts including WOFF
- Support for OOPP (Out-of-process plugin execution)
Users will find a slightly more conservative approach to changes in the user interface in the Pale Moon browser. It, although very close to Firefox, is (now more obviously so than before) a different product. However, these differences in layout do not prevent anyone from configuring their browser interface to exactly the way they want it to look and work. Including like Mozilla Firefox’s default layout if they so wish.
- Updated the included site-specific user-agent overrides for a number of websites that need them.
- Rewritten the browser’s padlock code to use more modern APIs and provide more accurate security status indication.
- Now also with localized tooltips!
- Fixed a missing close button on the undo prompt after removing a thumbnail from the QuickDial new tab page.
- Fixed an issue with the alternative stylesheet menu in the browser’s UI not working.
- Implemented the use of intrinsic aspect ratios for images to improve layout during load and page positioning.
- Added a preference to the use of node.getRootNode and disabled by default. See implementation notes.
- Added CSS -webkit-appearance as an alias for -Moz-appearance to improve compatibility with websites that only try to use Chrome-specific keywords to style standard form elements.
- Updated the SQLite library to 3.33.0.
- Changed media errors to be a more generic response, and added a preference (media.sourceErrorDetails.enabled) to enable detailed error reporting of media errors for debugging purposes.
- Previously, detailed errors were provided by default which could lead to privacy issues.
- Improved code stability of the AbortController implementation.
- Fixed a race condition in the secure connection library (NSS).
- Security issues fixed: CVE-2020-15664, CVE-2020-15666, CVE-2020-15667, CVE-2020-15668 and CVE-2020-15669.
- Unified XUL Platform Mozilla Security Patch Summary: 4 fixed, 1 defense-in-depth, 1 rejected, 9 not applicable.
- In 28.11.0 we introduced node.getRootNode because some websites would fail with an error if this function was not present. Unfortunately, this caused problems with other sites that (incorrectly) assume Google WebComponents are available when this utility function is present (feature detection has gone wrong). While it is considered by some to be part of the Google WebComponents implementation, it actually has utility value outside of that use. Because of the problems caused, we’ve added a preference and disabled it by default, fixing these kinds of websites.
- When needed, you can re-enable this function with dom.getRootNode.enabled
This should improve web compatibility by default yet still allow users to enable this function for websites that use its utility but do not use WebComponents.
Minimum System Requirements:
- Windows 7/8/10/Server 2008 R2 or later
- A processor with SSE2 instruction support
- 1 GB of RAM
- At least 200 MB of free (uncompressed) disk space
Size: 33.3 MB