We posted a question about this issue last week, and never received a response (thrilled at how actively telerik seems to patrol their forums - maybe they just don't like RedSox fans :)).
We have a radEditor, works absolutely fine in FF, doesn't work at ALL in IE. Any ideas?
I can provide a test URL if absolutely necessary, and code as well. I was just trying to determine if this is a known issue, or if we're doing something silly that's screwing our editor up.
TIA.
We have a radEditor, works absolutely fine in FF, doesn't work at ALL in IE. Any ideas?
I can provide a test URL if absolutely necessary, and code as well. I was just trying to determine if this is a known issue, or if we're doing something silly that's screwing our editor up.
TIA.
3 Answers, 1 is accepted
0
Accepted
Schlurk
Top achievements
Rank 2
Rank 2
answered on 17 Aug 2009, 07:38 PM
I'd be very sad if Telerik didn't like Sox fans :(
Anyways, from what I know the editor should work in IE8. I do know that if you have a version of the .dll that came out before IE8 did you can run into some issues, so I guess the first thing I could recommend is to see if you have the latest version of the editor. Also, you could see if the following demo works in your configuration of IE8 that is making this error occur:
http://demos.telerik.com/aspnet-ajax/editor/examples/editorinradwindow/defaultcs.aspx
If that works then it seems like the editor should work in IE8.
Anyways, from what I know the editor should work in IE8. I do know that if you have a version of the .dll that came out before IE8 did you can run into some issues, so I guess the first thing I could recommend is to see if you have the latest version of the editor. Also, you could see if the following demo works in your configuration of IE8 that is making this error occur:
http://demos.telerik.com/aspnet-ajax/editor/examples/editorinradwindow/defaultcs.aspx
If that works then it seems like the editor should work in IE8.
0
Neil
Top achievements
Rank 1
Rank 1
answered on 17 Aug 2009, 07:41 PM
yep. that friggin worked just fine - of course. Hrmmm that means its something WE did......
Thank you - at least now I know where the problem lies.
Thank you - at least now I know where the problem lies.
0
Schlurk
Top achievements
Rank 2
Rank 2
answered on 17 Aug 2009, 07:50 PM
You're quite welcome. Just make sure you have the latest version of everything before you try to find the problem, it might save a ton of time. Other than that I can just wish you good luck with finding the issue!