I think (but haven't verified) that three of the four messages in the examples are not FxMS messages, which is part of the problem.
> We think that most of these scenarios could be resolved
Yes, but mostly (only?) for messages that are part of the messaging system, so we need to make sure that as we talk about this, we're setting expectations correctly.
A big part of this enhancement is that if you decide to build your new message in FxMS, by default, it won't conflict with any other message in FxMS. This accelerates compounding FxMS user value by getting more new messages built into the system from the start.
Bug 1901797 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think (but haven't verified) that three of the four messages in the examples are not FxMS messages, which is part of the problem.
> We think that most of these scenarios could be resolved
Yes, but mostly (only?) for messages that are part of the messaging system, so we need to make sure that as we talk about this, we're setting expectations correctly.
A big part of this enhancement is that once we do this, if you decide to build your new message in FxMS, by default, it won't conflict with any other message in FxMS. This accelerates compounding FxMS user value by getting more new messages built into the system from the start.