I hit an issue in a site where the user had a mailto link in content structure like so...

 

mailto:someone@somesite.com?Subject=Website Order&Body=PLACEHOLDER%0APoster 003%0ABe Conscious of Your Work Environment

Dear jmercker,

 

Please refer to http://cutesoft.net/forums/post/33469.aspx

 

Regards,

Eric

Thanks for the reply and the post.  My problem isn't that the initial & gets replaces with & it's that on successive postbacks/saves, the CuteEditor keeps doing the replacement on & with & (e.g. it isn't recognizing that the substitution has already taken place).  In a scenario where the ampersand has already been encoded, the editor should not modify the URL at all.  It seems like the editor logic is doing simple substitution on the string (e.g. replace all & with &) rather than only replacing & where it's not already &

 

Am I missing something?

 

Thanks!

Jeramie

Dear jmercker,

 

I cannot reproduce this issue. Can you reproduce it in http://cutesoft.net/example/general.aspx?  Please tell me the reproduce steps.

 

Regards,

Eric 

Hi Eric,

 

I can repro it at the location you provided.  Here are the steps to repro.

 

1) Select any text you want in the demo + then use the link toolbar button to hyperlink the text. 

 

2) For the link, use this:  mailto:someone@somesite.com?Subject=Website Order&Body=PLACEHOLDER%0APoster 003%0ABe Conscious of Your Work Environment

 

3) Save the link and note the ampersand between Order and Body.

 

4) Click the save button on the toolbar.

 

5) Open the properties for the link created in #2.  Note that the & between Order and Body has now become &

 

6) Close the link properties dialog and click the Save toolbar button again.

 

7) Repeat 5 + 6, but note that the previous & has now become &

 

8) If you continue to click the save button and check the link properties, you'll see that the ampersand replacement will continue on N times where N is the number of times you click the save button.  In the above scenario, the & should only have been replaced once.

 

This is causing a problem in one of our projects as the substitution behavior is causing the Body portion of the mailto link to be ignored by the mail client.  If W3C has a recommendation on mailto links, I'd like us to be able to follow that recommendation, but still have the link work.  I think that if you can fix the substitution behavior, we'll get the best of both worlds.

 

Thanks!

 

Jeramie

Has any solution or work around come out for this?  I am running into the same problem with our system.

 

I can live with disabling the mailto encoding if that will solve the problem.

 

Thank you

Andrew