Closed
Bug 455390
Opened 16 years ago
Closed 16 years ago
nsIMsgCopyService.CopyMessages and nsIMsgFolder.deleteMessages fail with recent trunk builds
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: eyalroz1, Unassigned)
Details
Attachments
(1 file)
46.95 KB,
application/x-xpinstall
|
Details |
I'm using nsIMsgCopyService.CopyMessages to move messages from a source folder to the trash. Same code used to work on earlier SM trunk builds and works on TB 2.0.0.x . All arguments seem to be in order... still, I'm getting: Error: Could not convert JavaScript argument arg 1 [nsIMsgCopyService.CopyMessages] = NS_ERROR_XPC_BAD_CONVERT_JS Source file: chrome://removedupes/content/removedupes-common.js Line: 332 (attaching my extension's build so you could trigger this too; use it on a folder with some dupes and try removing them.)
Reporter | ||
Updated•16 years ago
|
Summary: nsIMsgCopyService.CopyMessages → nsIMsgCopyService.CopyMessages fails with recent trunk builds
Reporter | ||
Comment 1•16 years ago
|
||
Seeing the same thing with Error: Could not convert JavaScript argument arg 0 [nsIMsgFolder.deleteMessages] = NS_ERROR_XPC_BAD_CONVERT_JS Source file: chrome://removedupes/content/removedupes-common.js Line: 309
Summary: nsIMsgCopyService.CopyMessages fails with recent trunk builds → nsIMsgCopyService.CopyMessages and nsIMsgFolder.deleteMessages fail with recent trunk builds
Comment 2•16 years ago
|
||
Bug 435290 changed the second argument of CopyMessages from nsISupportsArray to nsIArray; CopyFolders in that interface also changed. nsIMsgFolder::deleteMessages has also changed in a similar fashion. Therefore you need to update your extension.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•