Rated 4 out of 5 stars

by Mark van Renswoude on May 13, 2011 ·

Simple and does what we want, excellent!

However, the signature bug mentioned in another review also occured on our 3.1.10 setups. We have multiple accounts with different signatures, and it always selects the signature of the active account instead of the default one which NoComposeAccount selects.The fix appears to be very simple; I added a line in constructor.js right after "obj.selectedIndex = i;" which says: "obj.click();". Works fine, haven't found any issues with it yet, though I must say it's the first time I did anything with a Mozilla extension, so I can't be sure.

Update: ok, so it's still buggy. If you move from the editor to the subject or anywhere else and back, it reverts the account to the default. I haven't tested it with the unmodified extension, but I'll assume my change is to blame.

This review is for a previous version of the add-on (1.0). 

by mital (Developer) on June 19, 2011 ·

...for taking the time to write a few lines.
I think I misunderstood the previous bug report about the signature issue since a quick test just now got me the same result.
The add-on needs to override the behavior that handles the insertion of signatures.
I'll give a look and try to fix it.
Also, I've added a support email address to the add-on listing. If you see this feel free to send me an email, and I'll keep you posted on the progress.