Pale Moon 32.1.0 Download | TechSpot

Why settle for a base build of your Firefox browser on Windows operating systems when you can get a version that runs 25% faster? Mozilla does not provide optimized browser packages for Windows, while many Linux (from scratch) users benefit from a browser built specifically for their system. This needs to be changed! So, here’s the Pale Moon project: custom-built and optimized Firefox browsers for Windows operating systems. Make sure your browser is using the maximum speed.

Of course, getting a faster browser isn’t just about optimizing the compilation process (building a program from source code), but also about carefully choosing features and getting the best settings. This means that this browser, as close as it is to Firefox, does not have all the features that Firefox has. Several carefully selected features have been disabled that are not in high demand and do not interfere with the display or functioning of web pages; all to maximize the speed and efficiency of the browser. Please visit the technical details page to find out exactly what the browser supports and what it doesn’t. In short, if you need accessibility or parental controls, visit the Firefox homepage and get the official unoptimized build.


  • Highly optimized for modern processors
  • 100% Firefox source code: as secure as a browser that has been developed over the years.
  • Uses slightly less memory due to disabled redundant and extra code.
  • A significant increase in the speed of drawing pages and processing scripts.
  • Support for SVG and Canvas.
  • Support for Firefox extensions, themes and profiles.

What’s new

This is another major update with important web compatibility improvements. In particular, our implementation of Google Web Components is now in a state where we have them enabled by default.

Additionally, our Mac builds (for both Intel and ARM Macs) are no longer in beta and are considered stable. Signed/notarized builds with custom branding available on the download page!

Huge thanks to FranklinDM for his work in this cycle that has brought us to this point. Of course, a big thank you to everyone who has contributed to this complex and difficult task of Web Components over time! Thanks also to Martok and Job Bautista for continuing to work on and improving the JavaScript engine, and to u3shit for working on improving video playback.


  • Shadow DOM and CustomElements, which together make up web components, have been enabled by default, which should provide much broader web browser compatibility for many sites using web frameworks 2.0+. See implementation notes.
  • Browser tab titles now disappear if they are too long instead of ellipsis to provide a bit more room for page titles to read. Please note that this may require some updates to tab extensions or themes.
  • A number of site-specific overrides have been updated or removed as they are no longer needed or relevant as the platform evolves in terms of web compatibility. We could use your help in evaluating those that are still there; see the issue in our repo.
  • Updated our promises and implementation of the async function to the current spec.
  • Promise.any() implemented
  • Fixed several crashes related to regex code.
  • Improved handling of regex objects so they can be properly garbage collected.
  • Fixed playback of some VP8 videos.
  • Fixed an issue where the insertion cursor (text cursor) would sometimes not display properly.
  • Updated built-in emoji font.
  • CSS pseudo-classes :is() and :where() are implemented.
  • Implemented complex selectors for the :not() CSS pseudo-class.
  • Implemented shorthand CSS inset property.
  • The env() environment variable CSS function has been implemented. See implementation notes.
  • Implemented video playback processing in RGB encoding (instead of just YUV).
  • Implemented full-range video processing (brightness levels 0-255) for better video playback.
  • Removed preinstalled WebP image decoder. See implementation notes.
  • Text-to-speech Web API is enabled by default (only supported on some operating systems).
  • Updated NSPR to 4.35 and NSS to 3.79.4.
  • Removed unused “tracking protection” plumbing. See implementation notes.
  • Removed URI classifier plumbing (remnants of Google SafeBrowsing).
  • Fixed several intermittent and hard to track crashes.
  • Improved jar content type security: channels. Did
  • Improved security of JIT JavaScript code generation. Did
  • Fixed possible crash scenarios in the graphics subsystem. Did
  • Improved filename security when saving files to prevent potential environment leaks.
  • Fixed security issues: CVE-2023-25751, CVE-2023-28163, and several others that do not have CVE.
  • Summary of Mozilla UXP security fixes: 1 fixed, 4 DiD, 14 not applicable.

Implementation Notes:

  • Google WebComponents has been working on the core features of UXP for a long time. Finally we have reached the level (after several failures and stone walls) that it can be enabled by default. Please note that while this greatly improves web compatibility with many Chrome-centric websites using these conflicting technologies, our implementation is not yet complete and more work is required. As a result, this change to enable it by default may actually break some previously running websites, but most are expected to work in our current state of implementation. Please visit the forum if you need help with web compatibility issues.
  • The env() CSS function was implemented for compatibility with websites that rely on it without fallback. Note that this feature doesn’t really have a real use for desktops, as it’s mostly used to denote environmental limitations of mobile screens, such as extra space needed to avoid a camera notch or folding screen bezel. However, due to the fact that some sites implement their styles in a mobile-first approach, this feature is expected to be available on all systems and browsers of those sites. Note that Pale Moon is simply hard-coding the requested values ​​here.
  • WebP images have long had a stable and complete implementation in Pale Moon, so the preference to disable support for it has been removed as it is considered one of the “major” image formats supported by web browsers for now. This was done to make content negotiation easier, especially as we’re adding additional JPEG-XL support that’s not yet complete. From now on, we just always support WebP decoding.
  • While we favored “tracking protection” in our browser implementation (in about:config), we never used this salable Firefox feature because it is mostly a service feature, and non-service parts were undesirable because they hurt harm to useful API. Our effective tracking protection has not changed, we have simply removed the preference and association with a non-functional service function that could potentially give the false impression that it does something.
  • As a reminder, if you are concerned about being tracked, use a competent ad blocker extension and enable “Tell sites not to share or sell my data” in Settings -> Privacy under Data Privacy. You can also enable “canvas poisoning” by setting canvas.poisondata to true in about:config to reduce the risk of fingerprinting through canvases.

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button