onMoved, onCopied events not fired when target folder is of imap type
Categories
(Thunderbird :: Add-Ons: Extensions API, defect)
Tracking
(Not tracked)
People
(Reporter: leon.botros, Unassigned)
Details
Attachments
(1 file)
|
689 bytes,
application/x-xpinstall
|
Details |
Steps to reproduce:
- make sure the extension has the right permissions (
accountsRead,messagesRead,messagesImport,messagesMove, etc.). - create a local folder and add a message to it (e.g., via
browser.messages.import()or by hand), - create an imap folder (I tested with a gmail account),
- create a listener in the background script (via, e.g.
browser.messages.onMoved.addListener()), - move the message from the local folder to the imap folder via
browser.messages.move(id, imapFolder)
Actual results:
The listener from step 3 does not receive the event.
Expected results:
The listener should receive the event, including event data about what message was moved where.
|
||
Comment 1•3 years ago
|
||
Note: This is independent of using messages.import(). Existing messages encounter the same behaviour.
|
||
Comment 2•2 years ago
|
||
I just discovered the same limitation, while testing the new version of the add-on Deselect on Delete:
When a message is manually moved from a folder of a first account (IMAP / POP / LOCAL) to a folder of a second account (IMAP), then the events messenger.messages.onMoved() and messenger.messages.onCopied() are not fired.
|
|
||
Comment 3•2 years ago
|
||
Created a basic reproducer add-on, which shows a notification whenever onMoved() and onCopied() are fired. This might help debugging the issue.
|
|
||
Comment 4•1 year ago
|
||
I am sorry for creating a new bug for this. Even though this bug was created much earlier, I am going to close this in favor of Bug 1923421 (where this is being fixed).
Description
•