Messages
Reply
Edit
Delete
If you want to replace the script tags in javascript, you are going to have a fair amount of custom coding to do - no fun!
--hm
Harvey - speaknig of ceditor. How do you train it not to disrupt <% and <%=. do you manage that in method code?
After doing a bit of searching, I discovered a documented fix for this problem. The link to the source is:
http://dev.ckeditor.com/changeset/7666
and documents the following original and change code:
var sBrowserVersion = navigator.appVersion.match(/MSIE (.\..)/)[1] ; replaced by var sBrowserVersion = navigator.appVersion.match(/MSIE ([\d.]+)/)[1] ;
After testing, I found the error to have gone away.
--hm
For some reason an application that has worked for about four or five years seems to have developed a problem. Not sure when the problem started since the page with this control is not used a lot by me and no other users have reported an error.
I'm getting an error in fckeditor.js function FCKeditor_IsCompatibleBrowser and because I'm using IE 10, I decided to change the compatibility to 9 and see if the problem went away. It did, so I looked further at the script code and found what looks like an error is in the match statement below.
var sBrowserVersion = navigator.appVersion.match(/MSIE (.\..)/)[1] ;
The error I see talks about "Unable to get property '1' of undefined or null reference". I assume this is because the first value (the major version number) is now two digits "10.0"
Is anybody having this problem or has everyone dropped this control or upgraded to a new version?
Thanks in advance for any suggestions.
--hm
--hm--