As mentioned in bug 516679, the code that resides in mailnews/extensions/smime mail/extensions/smime doesn't really equate to an extension any more. We should consider merging it into the rest of the mailnews code base so that we've not got unnecessary overlays and code that make it easy to miss things (like the fact that caused bug 515729 in the first place).
Additionally, saving an overlay also saves a bit of performance, AFAIK :)
(In reply to comment #0) > As mentioned in bug 516679, the code that resides in > > mailnews/extensions/smime > mail/extensions/smime > > doesn't really equate to an extension any more. While we don't ship without S/MIME at all these days, having it structured to cleanly use extension points ensures that we keep the extension points working so that other similar features (eg Enigmail) can use them well. It strikes me that the problem that caused bug 516679 wouldn't happen again now that the S/MIME code between SeaMonkey and Thunderbird has completely forked, rather than living in it's previous partially forked state. Actually getting rid of the extension structure strikes me as throwing out the baby with the bathwater. I suggest WONTFIX.
And it seems there are still only about 4 files from SMIME forked between SM and TB so much of the code can be shared. Merging it into the compose files somewhere would remove the sharing and allow unnecessary diverging (even when not needed due to functionality/XUL elements differences). I still do not understand why there must be so much divergence e.g. in the compose code (and thus these SMIME overlays) between SM and TB. I would merge them back if I could :)
You need to log in before you can comment on or make changes to this bug.