Known issues in the current versions
Development notes
The
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 all versions:
- The browser creates directories under %APPDATA%\Mozilla,
specifically Mozilla\Extensions
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 3.6.28:
None
Known issues in 9.1:
- Printing doesn't work correctly on some systems.
On some
systems, printing will only print the graphic elements of a page, but
not the text, when printing. The cause of this behavior is related to
hardware accelerated font rendering, and impacts any
browser that uses this kind of hardware acceleration when run on the
same systems (including IE 9, etc). I am unable to reproduce this
problem, myself, and I gather it may be related to not using a
dedicated graphics card. Exact causes are still unknown.
Workaround: Disable
(parts of) the hardware acceleration. More information here
on how to do that.
Workaround (alternative):
Use a graphical page capture add-on that allows direct printing.
Suggested: Fireshot https://addons.mozilla.org/en-US/firefox/addon/fireshot/
Status: [No ready way to fix this - use
workarounds]
- If there are a lot of animated images (animated GIFs etc.)
on a page, the browser will use a lot of processing power.
This is caused by a major bug in the underlying Firefox code (in the graphics libraries) that has to be addressed. Workaround: none, but if it's breaking for you, use 3.6.x.
More information:
Status: [Fixed]
Timeline: To be implemented in version 11
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:
3.6.23/24:
- Some sites complain that the browser is too old, while it
isn't. This is caused by a change in the UserAgent string in these
versions that is (inappropriately) used for determining browser
capabilities (so-called UserAgent-sniffing).
Status: [Fixed]
Timeline: to be implemented in Pale Moon 3.6.25
9.0:
- This version suffers from a speed regression due to a failed source branch merge.
Note: 9.0 has not been released to the public as a result. Status: [Fixed]
Timeline: Fixed in 9.0.1
9.0.1
- When upgrading, if the add-on compatibility assistant pops
up at first run, the Pale Moon status bar add-on can be listed as a
"Third Party Add-on" which will be deselected by default. The assistant
currently does not support a whitelisting feature to make an exception
for the core add-on.
Workarounds:
Status: [Fixed]
Timeline: Fixed in version 9.1.
- The
Pale Moon status bar component doesn't work when you
set the status to use "pop-up" notifications (instead of putting status
and links in the status bar). This is caused by slightly outdated code
in the extension that is incompatible with the Firefox 9 code.
Workaround: install a replacement Pale Moon status bar component. Instructions and download here:
http://forum.palemoon.org/viewtopic.php?f=1&t=411
Status: [Fixed]
Timeline: Updated add-on will be included in the next release.
[<-back]
Firefox,
Mozilla Firefox and Mozilla are registered trademarks of the Mozilla
Corporation.
Site and contents ©
2009-2012 Moonchild Productions - All rights reserved
Pale Moon's distribution is subject to the following redistribution policy
|