Changes between Initial Version and Version 3 of Ticket #2488


Ignore:
Timestamp:
Aug 22, 2008, 4:00:12 PM (11 years ago)
Author:
Alfonso Martínez de Lizarrondo
Comment:

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

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2488

    • Property Cc antonio@… added
    • Property Keywords Confirmed IE added; mailto removed
    • Property Component changed from UI : Floating Panel to General
    • Property Summary changed from Encode email "mailto:" links (Fix #220) to Encode email "mailto:" links (Fix #2220)
  • Ticket #2488 – Description

    initial v3  
    1 This regards Fix #220, adding the javascript based encryption of mailto links.
     1This regards Fix #2220, adding the javascript based encryption of mailto links.
    22
    33This 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:
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy