This does indeed appear to be a duplicate of bug 1563452. The extra encoded spaces do not occur in the editor, they happen when the message is serialized for sending due to that bug. I don't see much we can do here maybe try not using the `nsIDocumentEncoder::OutputFormatted` flag? https://searchfox.org/comm-central/source/mailnews/compose/src/nsMsgCompose.cpp#1099
Bug 1707360 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This does indeed appear to be a duplicate of bug 1563452. The extra encoded spaces do not occur in the editor, they happen when the message is serialized for sending due to that bug. I don't see much we can do here maybe try not using the `nsIDocumentEncoder::OutputFormatted` flag? https://searchfox.org/comm-central/source/mailnews/compose/src/nsMsgCompose.cpp#1099 I don't think decoding and encoding will have an effect because assigning a url to href seems to ensure the value is encoded regardless.
This does indeed appear to be a duplicate of bug 1563452. The extra encoded spaces do not occur in the editor, they happen when the message is serialized for sending due to that bug. I don't see much we can do here maybe try not using the `nsIDocumentEncoder::OutputFormatted` flag? https://searchfox.org/comm-central/source/mailnews/compose/src/nsMsgCompose.cpp#1099 I don't think decoding and encoding will have an effect because setting an anchor's href seems to ensure the value is encoded regardless.
This does indeed appear to be a duplicate of bug 1563452. The extra encoded spaces do not occur in the editor, they happen when the message is serialized for sending due to that bug. I don't see much we can do here maybe try not using the `nsIDocumentEncoder::OutputFormatted` flag? https://searchfox.org/comm-central/source/mailnews/compose/src/nsMsgCompose.cpp#1099 I don't think decoding and encoding will have an effect because setting an anchor's href seems to ensure the value is properly encoded regardless.
This does indeed appear to be a duplicate of bug 1563452. The extra encoded spaces do not occur in the editor, they happen when the message is serialized for sending due to that bug. I don't see much we can do here maybe try not using the `nsIDocumentEncoder::OutputFormatted` flag? https://searchfox.org/comm-central/source/mailnews/compose/src/nsMsgCompose.cpp#1099 I don't think decoding and encoding will have an effect because setting an anchor's href seems to ensure the value is properly encoded regardless. Thomas note: I don't think this has to do with the url length. Try adding a link to "http://www.example.com/foo ba r.pdf" and you will get the same result. See bug 1563452 comment 14.