A "catch all" component for problems found when using the SeaMonkey suite which do not fall into one of the current components. Example: launch/exit crashes, features missing, etc.
PLEASE NOTE!! Try to find a component which is specific to your bug first - BEFORE assigning to this component!

I'm note sure this is a duplicated of Bug 919018.
In Bug 919018 CalDAV is reported broken because the http.jsm module is missing in SeaMonkey 2.21. In this report I used SeaMonkey 2.22 that was build several weeks after Bug 884319
was fixed and that should contain the http.jsm module. In addition I did not saw any error messages as written in comment #0.
More testing and feedback from SeaMonkey users would be nice.

Seamonkey is missing browserRequest.* and its artwork. I've tested this by manually injecting the files into a Seamonkey nightly and I must admit this patch is totally untested. Nevertheless, I hope I've copied all the files into the right locations.
I'd appreciate if you could give this patch a test run.

I understand that the files copied from Thunderbird may not be in good shape, but I really just created this patch as a quick copy from TB to SM so that users are happy. I didn't expect this to be a full cleanup, which would mean clean up in TB, SM and IB together. Is there any chance you'd r+ the patch with just the Seamonkey related bits fixed, i.e copying the icons from winstripe instead?

Comment on attachment 8400232[details][diff][review]
Fix - v1 [check-in comment 13][c-a,c-b check-in comment 16]
(In reply to Philipp Kewisch [:Fallen] from comment #9)
> I understand that the files copied from Thunderbird may not be in good
> shape, but I really just created this patch as a quick copy from TB to SM so
> that users are happy. I didn't expect this to be a full cleanup, which would
> mean clean up in TB, SM and IB together.
Sorry for getting carried away. r=me for landing in suite on condition you file a followup bug to fix the issues detailed Comment 8. I'll probably work on getting it into shape and then moved to shared /mailnews/
> patch with just the Seamonkey related bits fixed, i.e copying the icons from
> winstripe instead?
Sure.

> Sorry for getting carried away. r=me for landing in suite on condition you
> file a followup bug to fix the issues detailed Comment 8. I'll probably work
> on getting it into shape and then moved to shared /mailnews/
I guess I can reuse this bug for follow-up patches after you get ui-r from Neil().

Comment on attachment 8400232[details][diff][review]
Fix - v1 [check-in comment 13][c-a,c-b check-in comment 16]
Well, that was awful.
First, I accidentally created the calendar while I was offline. Nothing happened. I couldn't find out how to access the calendar after creating it, nor could I delete the calendar, so I resorted to deleting all calendar prefs from prefs.js just so that I could recreate the calendar so as to trigger the authentication.
The window that was opened wasn't sure whether it was supposed to be a dialog. It had the title bar height of a regular window, but the lack of window features of a dialog. It was also always on top of other windows from the same application, so I couldn't easily switch to, say, DOM Inspector. It also had no title.
The window included something that seemed to want to resemble a URL bar, but it had a strange icon and was poorly themed. DOM Inspector showed that the URL wanted to wrap although its overflow had been hidden not once, but twice.