If we introduce a message-open-API, and a developer links that to a menu entry which he added to the context menu of the message list, it should open the exact message clicked on. Otherwise, the UI could jump to a different folder which would be highly confusing. I am totally fine with adding the capability to open mid: urls by extending the function we already have but finding a better place and name, but we also need a dedicated message open function (part of the messages API), which is ID driven and allows specifying how it should be opened (tab, preview, window).
Bug 1603489 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
If we introduce a message-open-API, and a developer links that to a menu entry which he added to the context menu of the message list, it should open the exact message clicked on. Otherwise, the UI could jump to a different folder which would be highly confusing. I am totally fine with adding the capability to open mid: urls by extending the function we already have but finding a better place and name, but we also need a dedicated message open function (part of the messageDisplay API), which is ID driven and allows specifying how it should be opened (tab, preview, window).