Known issues in the current version
Pale Moon browser, at any point in time, may have a number of known
issues. These known issues will usually be addressed in the next
release of the browser, or it may be something that people have noticed
and are mentioned here because they are "by design", i.e.: issues
people have asked about, are known, and are this way on purpose.
For each issue, check the status for intended action to be taken in
development (if any) and intended timeline (if applicable).
Known issues in 20.0.1:
- On certain systems, rendering of text and graphics may become "pixelated"
If you are using Windows 7 SP1 with the recently (Feb 28th 2013) released Windows Platform Update (KB 2670838),
or potentially also if you are using Windows 8, and your system is
equipped with an ATI/AMD Radeon HD3000 or HD4000 series graphics
processor, you may encounter issues with rendering text and graphics in
page content, similar to:
This is caused by the combination of OS, the Platform Update which
makes changes to DirectX acceleration, and the graphics
hardware/drivers in your system. Microsoft is still triaging this
issue, and has pulled the update as a critical update (it is currently
optional). Note that it may be installed as a prerequisite for using
Workaround: See http://forum.palemoon.org/viewtopic.php?f=1&t=2228
Known issues in the 3.6.* versions (Legacy, discontinued):
Known issues in all versions:
- Some sites render particularly slow or stall the browser, or don't display correctly.
This is caused by the websites in question using more modern website
coding, notably more advanced HTML5 and CSS3, that is not and will not
be supported by the Legacy version of Pale Moon (the Gecko rendering
engine used in this version does not properly support it).
Solution: Upgrade to the Next Generation version of Pale Moon (if your hardware and O.S. support it).
Status: [Inherent, won't fix]
- The browser creates directories under %APPDATA%\Mozilla,
These directories are related to the underlying Mozilla extension code
(Pale Moon is a Mozilla-based browser) and stores extension IDs there.
This issue is completely harmless and non-breaking; in fact, having
(all) Mozilla-based applications use this one central location
for extension IDs is desired.
Status: [By Design]
Known issues in previous versions
Because issues in previous versions may still apply to what people are
running, here is a recap of previous, still recent versions that have
been fixed, and potential workarounds:
- When selecting a bookmark to "Open in the sidebar" in the bookmark options, a parsing error is given instead of the page in the sidebar.
This is caused by a removed context menu item in the Firefox code base,
and Pale Moon lacking the proper definition of the restored item in the
Workaround: Download a replacement browser.jar here
and replace the browser.jar file in Pale Moon's installation chrome
folder (e.g. C:\Program Files\PaleMoon\chrome) with the one in the .zip
Timeline: Fixed in Pale Moon 19.0.1
- Some CSS/HTML combinations cause the browser to hang.
This is caused by a rendering issue in the Direct2D back-end, which
occurs on certain systems with relatively poor CSS/HTML page design.
Workaround: In about:config, set gfx.direct2d.disabled to true and restart the browser.
Timeline: Fixed in Pale Moon 15.4
Mozilla Firefox and Mozilla are registered trademarks of the Mozilla
Site and contents ©
2009-2013 Moonchild Productions - All rights reserved
Pale Moon's distribution is subject to the following redistribution policy