Noticed in bug 670976 comment 26. There is duplicated code in folderWidgets.xml._setCssSelectors, which is already defined in /mailnews/base/util/folderUtils.jsm getSpecialFolderString().

Comment on attachment 597967 [details] [diff] [review] patch thx, this does seem to fix the aFolder error (that was the intent, right?). I've requested a try server build to make sure mozmill tests still pass, but it looks good to me.

No, this will actually confuse the debugging even more, it should now throw inside getSpecialFolderString, where aFolder.flags is accessed. Attempt to solve the error is properly separated in bug 670976.

This bug is just code-deduplication, no behaviour change intended.

(In reply to :aceman from comment #3) > No, this will actually confuse the debugging even more, it should now throw > inside getSpecialFolderString, where aFolder.flags is accessed. that exception seems to get caught and suppressed; I don't see anything on the error console anymore.

If you didn't apply patch from bug 670976 too then it would be strange. The change here should not have the effect of suppressing it. Do you have proper STRs? Maybe exceptions are hidden inside .jsm files? Just place an alert (or other dump) before the line 'aMenuNode.setAttribute("SpecialFolder", getSpecialFolderString(aFolder));' and you should see aFolder is undefined.

So what are your results? What about the trybuild? This patch alone should not intentionally hide the error.

(In reply to :aceman from comment #7) > So what are your results? What about the trybuild? > This patch alone should not intentionally hide the error. turns out my STR's (the run message filter steps) were not reliable, though I did try it a couple times w/ and w/o the patch. So ignore me.

So does the r+ hold?

(In reply to :aceman from comment #9) > So does the r+ hold? sure, it's good to remove the code duplication, thx.

Checked in: http://hg.mozilla.org/comm-central/rev/d182f15b6b63