Created an attachment (id=7462) [details]
Screenshot of QF

I recently did a re-install of TB and I noticed several broken behaviors:

1. The paint mode will not shut off without a restart.

2. The folders will not display correctly. The only way that they will show is
if the mouse is hovered over them.

3. The folders will not color correctly. All that shows is a line at the top of
the (not showing) folders.
3a. When hovered over all but the top colored line shows as dark grey/

I am enclosing a screenshot to show what I am seeing.

I should also note that I did download the patch and it didn't seem to help
much. Also, many of us refuse to downgrade to newer versions. 5 to whatever
broken version they are up to are garbage garbage garbage! I gave up on even
trying after about 8.

Created an attachment (id=7466) [details]
Screenshot of QuickFolders"ss is null" error

*** This bug has been marked as a duplicate of bug 25277 ***

Hm, AFAICT comment #1 is bug 25277 but comment #0 is not.

Paul: Using obsolete versions of Thunderbird is at your own risk only. Every
new release fixes some bugs (even if it sometimes breaks features that were
working before). If the problem you see does not happen in Thunderbird 17.0 or
later, then the problem was fixed, and the fix won't be ported to any earlier
version. In that case, if you absolutely don't want to upgrade to any "current"
version of the mailer, your only resource is to see if some obsolete version of
the extension will work with whatever obsolete mailer version you decided to
stay on.

I did switch to an older version and that didn't help. However, the rule about
ALWAYS updating software is a myth. The rule should be update MOST of the time-
as occasionally newer is worse- sometimes catastrophically bad(Windows Vista,
Windows 8, Freezefox 4+...) This also applies to TB. The 3 series flat out is
superior to the rabid-release versions. 

UPDATE. This is weird. I switched to 3.82 and it MOSTLY is working correctly.
In the options section the "Individual Tab Color Appearance" has reappeared and
the tabs now appear and are colored correctly- but only if the flat tabs are
selected. It would be nice if the others worked- but the flat tabs are a good
choice and the others would be a nice bonus. 

(In reply to comment #5)
> UPDATE. This is weird. I switched to 3.82 and it MOSTLY is working correctly.
> In the options section the "Individual Tab Color Appearance" has reappeared and
> the tabs now appear and are colored correctly- but only if the flat tabs are
> selected. It would be nice if the others worked- but the flat tabs are a good
> choice and the others would be a nice bonus. 
> 

This is actually "by design"; as if you use button or real tab style, it is not
possible to do the coloring. Also, in "Apple Pills" only the active tab shows
the individual colors, which again is by design of the original theme author.

I am afraid the bug may be caused by making it backwards compatible while
avoiding the deluge of unnecessary warnings that would be caused in the more
modern Gecko4+ versions that support CSS3 and where obsolete rules like 

-moz-box-shadow
-moz-border-radius
-moz-linear-gradient

are now replaced with the standardized css attributes

box-shadow
border-radius
linear-gradient

Ti get even more technical, I already had moved the deprecated styles to new
style sheets which are only loaded in older Tb versions (App version < 4) in
the previous version 3.8. Through multiple overlays the palette rules were
included multiple times, so I switched to an @import rule.

The problem is in the way that I need to iterate all active styles and (due to
my ignorance) import rules were not parsed properly, which caused problems with
the modern Thunderbirds. So the latest version tries to remedy it by also
iterating @import rules (which are part of the stylesheet's cssRules
collection) which should be done recursively. Also the latest version fixes
some problems in the options window which is styled in a different way (every
XUL window has its own overlays and global context). The problem was to find
the correct style sheet from the window, and obviously something also goes
wrong during startup (maybe the style rules are not loaded yet). To ind out
exactly I need to reproduce the problem maybe with SeaMonkey as I couldn't
reproduce it with Tb3.

As regards screenshots, can you instead include a screenshot of the gray line
or something as I am familiar with the error message. I can test with Tb 3.1.20
from a virtual machine.

Axel: if you include both rules in a single style sheet, e.g.

  { -moz-border-radius: 3px
  ; border-radius:      3px
  }

the browser will ignore whichever rule it does not recognize (and say so as a
warning in the error console) but it will use the other. For instance, the
table-of-contents box near top left of
http://users.skynet.be/antoine.mechelynck/vim/compile.htm (which has a "style"
attribute rather than a separate style sheet) should appear with rounded
corners in any browser which supports *either* -moz-border-radius *or*
border-radius.

(In reply to comment #7)
> Axel: if you include both rules in a single style sheet, e.g.
> 
>   { -moz-border-radius: 3px
>   ; border-radius:      3px
>   }
> 
> the browser will ignore whichever rule it does not recognize (and say so as a
> warning in the error console) but it will use the other. 

...and this will cause unnecessary warnings in error console. The way I have
set it up, only the outdated platform (Gecko<4) will get the warnings (about
the newer css rules). The old rules are not loaded at all for thunderbird 16
and greater; I am including the legacy rules only in
qf_legacy16.css
and
qf_palette_legacy16.css

this way I can also elegantly avoid problems during the validation (on upload)
- I simply tell the testers to ignore these files as they are not loaded with
the current Gecko versions.

I want to keep console warnings to an absolute minimum as they make it hard for
me and other addon authors to find out about _real_ issues.

bug also in SeaMonkey 2.14.1

minimum version for QF is Thunderbird 19.0. Not sure which version of SeaMonkey
should be supported (the install.rdf says 2.0)