Hi,
There is a bug in WebHtmlEditor 14.1.20141.2150 when using IE10:
Unable to get property 'open' of undefined or null reference (ig_htmleditor.js, line 2016).
Hello,
Thank you for posting in our forum.
In order to further look into this I’ll need some additional information.
Which are the exact steps that trigger the issue?
Are you encountering the same issue with the online sample at:
http://www.infragistics.com/samples/aspnet/html-editor/built-in-text-formatting-toolbars
If so, which is the specific version of IE10 on which you’re encountering the issue ?
If the issue is not reproducible in the online sample, this indicates a possible problem in the code of your application. It will help if you can provide a small, isolated sample application that demonstrates the behavior you are seeing.
I’m looking forward to your reply.
Best Regards,
Maya Kirova
Developer Support Engineer II
Infragistics, Inc.
http://www.infragistics.com/support
Thanks for your reply.
The online sample is working on IE10, but it's based on an old release (vs 12/06/13).
I followed the steps you suggested and was unable to reproduce the behavior you're describing. I’ve created a sample with a WebHtmlEditor and tested it on IE10 (version 10.0.9200.16921) however no error were thrown when testing this on my side.
I have attached the sample project I used to test this as well as a screenshot of the observer result. Please test this project on your PC; whether or not it works correctly may help indicate the nature of this problem.
If the project does not work correctly, this indicates either a problem possibly specific to your environment.
If the project does show the product feature working correctly, this indicates a possible problem in the code of your application. It will help if you can provide a small, isolated sample application that demonstrates the behavior you are seeing.
Or, if this sample project is not an accurate demonstration of what you're trying to do, please feel free to modify it and send it back, or send a small sample project of your own if you have one.
Please let me know if I can provide any further assistance.
Your sample project worked like a charm on IE10.
It seems that is more related to how we use it: An old release 11.2 with JavaScriptDirectory property set to JS scripts from 14.1.20141.2150 release.
This "hack" was working with 14.1.20141.1015 release.
Thanks for your help.
I’m glad to hear this solved your issue. If you have any additional questions or concerns please let me know.