Opened 16 years ago
Last modified 16 years ago
#2488 closed Bug
Encode email "mailto:" links (Fix #2220) — at Version 3
Reported by: | aspenwebdesign | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | FCKeditor 2.6.4 |
Component: | General | Version: | FCKeditor 2.6.3 Beta |
Keywords: | Confirmed IE Review+ | Cc: | antonio@…, Jani Ollikainen |
Description (last modified by )
This regards Fix #2220, adding the javascript based encryption of mailto links.
This fix causes problems in Internet Explorer. When you click on an encoded (by FCK) mailto link on the frontend of a website, it causes IE6 and IE7 to do two things:
- Open a new email window (what we want)
- Take the browser to a new page with "mailto:..." in the content (what we don't want)
This problem exists in IE, but not in Firefox or Safari (what else is new). It's possible this has been resolved in 2.6.3 (we're running 2.6.3 beta) but there is no mention of it.
Can someone kindly look into this? Thanks much for all your hard work!
Change History (3)
comment:1 Changed 16 years ago by
Cc: | antonio@… added |
---|
comment:2 Changed 16 years ago by
Summary: | Encode email "mailto:" links (Fix #220) → Encode email "mailto:" links (Fix #2220) |
---|
comment:3 Changed 16 years ago by
Component: | UI : Floating Panel → General |
---|---|
Description: | modified (diff) |
Keywords: | Confirmed IE added; mailto removed |
If you change the config to FCKConfig.EMailProtection = 'none' ;
you should get the old behaviour (and I think that it should be the default, because those encrypted links aren't usable by people with javascript disabled.
to fix the IE error, it seems that changing from <a href="javascript:location.href='mailto:'+String.fromCharCode(109,97,105,108,64,101,120,97,109,112,108,101,46,99,111,109)+'?'">
to <a href="javascript:void(location.href='mailto:'+String.fromCharCode(109,97,105,108,64,101,120,97,109,112,108,101,46,99,111,109)+'?')">
is enough
Hi, I confirm that the problem exists also on 2.6.3.
Moreover on my Firefox (an old one, is version 2.0.0.16) I get the following error:
I translate the error in english:
Is it possible to configure fck 2.6.3 in order to have the old behaviour?
Thank you very much for your work.