Open Bug 1849476 Opened 1 year ago Updated 3 months ago

messages.move/copy() doesn't set mail.last_msg_movecopy_target_uri

Categories

(Thunderbird :: Add-Ons: Extensions API, defect)

defect

Tracking

(Not tracked)

People

(Reporter: Fallen, Unassigned)

Details

When using messenger.messages.move(), the Move to "foldername" again menuitem is not updated. Not sure this should always be the case, but when it is a user-initiated move that the extension is executing, this would be useful.

There are discussions about adding undo support as well which also fits the user-initiated case. How about adding a flag to messages.move() to let the developer enable this user-initiated mode, which will handle the move operation identical to a move in the UI?

Any suggestions for the flag name?

Or would you rather suggest dealing with undo and the recent-moves-list separately?

I think the recent moves list should be updated automatically, not a separate function. In terms of the flag name, I'd go with something that describes the function instead of the technical detail, but I'd need to think on it a bit. My gut says userInitiated, and you'd have to consider if the default should be true or false. This would depend on if the most typical use case is user moves, or background moves.

You need to log in before you can comment on or make changes to this bug.